Tx hash: 1bd5aa3b4c7f7f38a212620a7ebe3beb406cbd08a75b99e7c25637259964ad6c
Tx prefix hash: c9f156288561279c3c045aa0646dfe8d385f2f2ada4f35c7a9bee515d18d7bf3
Tx public key: b606eba0a1329a8be06fe0a760bf11f19a87c3561c1bc6a125980c10a5229b5d
| Timestamp: 1779902047 | Timestamp [UTC]: 2026-05-27 17:14:07 | Age [y:d:h:m:s]: 00:003:02:28:50 |
| Block: 1268 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0811 kB |
| Tx version: 2 | No of confirmations: 2237 | RingCT/type: yes/0 |
| Extra: 01b606eba0a1329a8be06fe0a760bf11f19a87c3561c1bc6a125980c10a5229b5d | ||
1 output(s) for total of 35.093154652233 xmr
| stealth address | amount | amount idx | tag |
| 00: 3f9f5f1c1bde55f2f043b92281e79ccaa8e4858fd3d2f3e707a4f98e0cf2dfa5 | 35.093154652233 | 1256 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": 1328,
"vin": [ {
"gen": {
"height": 1268
}
}
],
"vout": [ {
"amount": 35093154652233,
"target": {
"key": "3f9f5f1c1bde55f2f043b92281e79ccaa8e4858fd3d2f3e707a4f98e0cf2dfa5"
}
}
],
"extra": [ 1, 182, 6, 235, 160, 161, 50, 154, 139, 224, 111, 224, 167, 96, 191, 17, 241, 154, 135, 195, 86, 28, 27, 198, 161, 37, 152, 12, 16, 165, 34, 155, 93
],
"rct_signatures": {
"type": 0
}
}