Tx hash: a13717009c40b289548d569a77ce58a9f5a1798783c488931e574105b3b85c9c
Tx prefix hash: 06540ace5861241b709cd2fc89480235bf1436d18a2fbfe150cf32c071ba01cf
Tx public key: 45c66fa4b015f2dc1dbfe557838f0ef9ebce7e5dd837cc186a8d66888b1e4fb7
| Timestamp: 1780117603 | Timestamp [UTC]: 2026-05-30 05:06:43 | Age [y:d:h:m:s]: 00:002:08:14:57 |
| Block: 3085 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0811 kB |
| Tx version: 2 | No of confirmations: 460 | RingCT/type: yes/0 |
| Extra: 0145c66fa4b015f2dc1dbfe557838f0ef9ebce7e5dd837cc186a8d66888b1e4fb7 | ||
1 output(s) for total of 34.971744362946 xmr
| stealth address | amount | amount idx | tag |
| 00: bb1d2e2ad4f292a5a1836838e5da31be8c5594fe7e0a13c6594a75e3ef02522d | 34.971744362946 | 3073 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": 3145,
"vin": [ {
"gen": {
"height": 3085
}
}
],
"vout": [ {
"amount": 34971744362946,
"target": {
"key": "bb1d2e2ad4f292a5a1836838e5da31be8c5594fe7e0a13c6594a75e3ef02522d"
}
}
],
"extra": [ 1, 69, 198, 111, 164, 176, 21, 242, 220, 29, 191, 229, 87, 131, 143, 14, 249, 235, 206, 126, 93, 216, 55, 204, 24, 106, 141, 102, 136, 139, 30, 79, 183
],
"rct_signatures": {
"type": 0
}
}