Tx hash: 58d1c708182d542c2ac3c31c765b2fff99358d9b9b3bf8377c354ef20fd79bfc
Tx prefix hash: c58cdd78e9c270b18b40b49664c0d05c1c7641967437c48f6e911485654a0aec
Tx public key: 3db85f48a00655bf72ec8e2348a2d58d5e388ec362e5c6f0b074180fa3ba8c7b
| Timestamp: 1780040520 | Timestamp [UTC]: 2026-05-29 07:42:00 | Age [y:d:h:m:s]: 00:003:11:48:33 |
| Block: 2433 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0811 kB |
| Tx version: 2 | No of confirmations: 1112 | RingCT/type: yes/0 |
| Extra: 013db85f48a00655bf72ec8e2348a2d58d5e388ec362e5c6f0b074180fa3ba8c7b | ||
1 output(s) for total of 35.015262015263 xmr
| stealth address | amount | amount idx | tag |
| 00: 4b73cbc4f2aa6e1d11225a8b89fb764c5543ec38510ec6ae1917f353ad9eea78 | 35.015262015263 | 2421 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": 2493,
"vin": [ {
"gen": {
"height": 2433
}
}
],
"vout": [ {
"amount": 35015262015263,
"target": {
"key": "4b73cbc4f2aa6e1d11225a8b89fb764c5543ec38510ec6ae1917f353ad9eea78"
}
}
],
"extra": [ 1, 61, 184, 95, 72, 160, 6, 85, 191, 114, 236, 142, 35, 72, 162, 213, 141, 94, 56, 142, 195, 98, 229, 198, 240, 176, 116, 24, 15, 163, 186, 140, 123
],
"rct_signatures": {
"type": 0
}
}