Tx hash: 06982b0755da128de52ae91b0f1c4a0d30deff23d992ff9dbd421a47c0a36831
Tx prefix hash: d9c450e441a3e21f6dfb67ffe525803603578433c5d526995ca86da7801a285e
Tx public key: 8d0c5fbc8714aafbaf83ea8a12d47b23bdd4e9d5867008dc651d0677dd55df8e
| Timestamp: 1780104390 | Timestamp [UTC]: 2026-05-30 01:26:30 | Age [y:d:h:m:s]: 00:000:15:54:39 |
| Block: 2971 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0811 kB |
| Tx version: 2 | No of confirmations: 473 | RingCT/type: yes/0 |
| Extra: 018d0c5fbc8714aafbaf83ea8a12d47b23bdd4e9d5867008dc651d0677dd55df8e | ||
1 output(s) for total of 34.979349374180 xmr
| stealth address | amount | amount idx | tag |
| 00: bb3b6fa1da5ea24a72444bf1353e4c4167c14eea8c352be627ddb7cd0ed1a77c | 34.979349374180 | 2959 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": 3031,
"vin": [ {
"gen": {
"height": 2971
}
}
],
"vout": [ {
"amount": 34979349374180,
"target": {
"key": "bb3b6fa1da5ea24a72444bf1353e4c4167c14eea8c352be627ddb7cd0ed1a77c"
}
}
],
"extra": [ 1, 141, 12, 95, 188, 135, 20, 170, 251, 175, 131, 234, 138, 18, 212, 123, 35, 189, 212, 233, 213, 134, 112, 8, 220, 101, 29, 6, 119, 221, 85, 223, 142
],
"rct_signatures": {
"type": 0
}
}