Tx hash: 48fb6eb9f32f938c973fd3f63c830abaeb5152ad2a6f51a1eee0ae70cce22c3d
Tx prefix hash: 2dbebc23f3e18b3c5bc7fcde6ecd0fa24979f222c6e24e0c181ff97da185fba5
Tx public key: fbe0fa618e276c547f2c2f39c90740a864a42d56fd16b1b57fe9a49b68922cc2
| Timestamp: 1778794163 | Timestamp [UTC]: 2026-05-14 21:29:23 | Age [y:d:h:m:s]: 00:011:20:34:21 |
| Block: 72 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0801 kB |
| Tx version: 2 | No of confirmations: 474 | RingCT/type: yes/0 |
| Extra: 01fbe0fa618e276c547f2c2f39c90740a864a42d56fd16b1b57fe9a49b68922cc2 | ||
1 output(s) for total of 35.173300224642 xmr
| stealth address | amount | amount idx | tag |
| 00: 013fcbea4cbbeaeedcf520c48f743a416dc3b64943f49223edbe1a11aecc245d | 35.173300224642 | 60 of 0 | - |
Check which outputs belong to given Monero address/subaddress and viewkey
For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side
Prove to someone that you have sent them Monero in this transaction
Tx private key can be obtained using get_tx_key
command in monero-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side
{
"version": 2,
"unlock_time": 132,
"vin": [ {
"gen": {
"height": 72
}
}
],
"vout": [ {
"amount": 35173300224642,
"target": {
"key": "013fcbea4cbbeaeedcf520c48f743a416dc3b64943f49223edbe1a11aecc245d"
}
}
],
"extra": [ 1, 251, 224, 250, 97, 142, 39, 108, 84, 127, 44, 47, 57, 201, 7, 64, 168, 100, 164, 45, 86, 253, 22, 177, 181, 127, 233, 164, 155, 104, 146, 44, 194
],
"rct_signatures": {
"type": 0
}
}