Tx hash: 0bd0aec169c4b0c49b5d64f0ae5b1d3f1ccf8b9d684c8dba389f0de4430b88af
Tx prefix hash: c063c93859dcdd1fcba28e7df55c73f922abc63e07aeb9c758fb8fbb09e52291
Tx public key: b55ca76dd924f7007e2622d70031e7e510a1d02039a495b0666453ad1d1f9aaa
| Timestamp: 1780078963 | Timestamp [UTC]: 2026-05-29 18:22:43 | Age [y:d:h:m:s]: 00:000:09:45:43 |
| Block: 2781 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0811 kB |
| Tx version: 2 | No of confirmations: 278 | RingCT/type: yes/0 |
| Extra: 01b55ca76dd924f7007e2622d70031e7e510a1d02039a495b0666453ad1d1f9aaa | ||
1 output(s) for total of 34.992028068187 xmr
| stealth address | amount | amount idx | tag |
| 00: 54d04dfb122d3637f95d267a16bc5a367af58c3d5d19d5b16a35a96b5abefb72 | 34.992028068187 | 2769 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": 2841,
"vin": [ {
"gen": {
"height": 2781
}
}
],
"vout": [ {
"amount": 34992028068187,
"target": {
"key": "54d04dfb122d3637f95d267a16bc5a367af58c3d5d19d5b16a35a96b5abefb72"
}
}
],
"extra": [ 1, 181, 92, 167, 109, 217, 36, 247, 0, 126, 38, 34, 215, 0, 49, 231, 229, 16, 161, 208, 32, 57, 164, 149, 176, 102, 100, 83, 173, 29, 31, 154, 170
],
"rct_signatures": {
"type": 0
}
}