Tx hash: 2bddcd5245dfe36782b35a2dfd591ff2d0a4fd85ef83e6ee20f6e4449a14b6a0
Tx prefix hash: 435a1d06adfe28cf76a383ca2dc729b3a8c987b3d002a8f67ea6ec404c561990
Tx public key: 06174e1a257f666b9c28e7d1a8420548d236130477a86944da804f814a3d783a
| Timestamp: 1779817722 | Timestamp [UTC]: 2026-05-26 17:48:42 | Age [y:d:h:m:s]: 00:001:11:07:13 |
| Block: 532 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0908 kB |
| Tx version: 2 | No of confirmations: 1071 | RingCT/type: yes/0 |
| Extra: 0106174e1a257f666b9c28e7d1a8420548d236130477a86944da804f814a3d783a0208c125e30bd4597c86 | ||
1 output(s) for total of 35.142453366213 xmr
| stealth address | amount | amount idx | tag |
| 00: 8b73e4166bcf2d16bebb09b03ad935d588e090ac1361b7f5783979678f81edd8 | 35.142453366213 | 520 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": 592,
"vin": [ {
"gen": {
"height": 532
}
}
],
"vout": [ {
"amount": 35142453366213,
"target": {
"key": "8b73e4166bcf2d16bebb09b03ad935d588e090ac1361b7f5783979678f81edd8"
}
}
],
"extra": [ 1, 6, 23, 78, 26, 37, 127, 102, 107, 156, 40, 231, 209, 168, 66, 5, 72, 210, 54, 19, 4, 119, 168, 105, 68, 218, 128, 79, 129, 74, 61, 120, 58, 2, 8, 193, 37, 227, 11, 212, 89, 124, 134
],
"rct_signatures": {
"type": 0
}
}