For RingCT transactions, outputs' amounts are also decoded
Tx private key can be obtained using get_tx_key
command in hashmonkey-wallet-cli command line tool
Tx hash: 4471a336570c946f08eaeceaa4b638c7a766ab3f6534a40509dc359e83bcdf82
Tx prefix hash: c6069ab6cdbbf20440034c82ecbc87e78119cadbf07147007e39e8f01f8fdd49
Tx public key: 5e9eece8d63e535b218484f195686566e0e28b7711203c08e0b83beeed91b4f6
| Timestamp: 1780690389 | Timestamp [UTC]: 2026-06-05 20:13:09 | Age [y:d:h:m:s]: 00:003:07:25:41 |
| Block: 5657 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2289 | RingCT/type: yes/0 |
| Extra: 015e9eece8d63e535b218484f195686566e0e28b7711203c08e0b83beeed91b4f6020900000001e49593ff00 | ||
1 output(s) for total of 34.806844035018 HMNY
| stealth address | amount | amount idx | tag |
| 00: 14a5b074eeade55e46e45499da8a52cc6e2bdd3197e9f138eda1a133718b9b54 | 34.806844035018 | 7106 of 0 | <e3> |
Check which outputs belong to given HMNY 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 HMNY in this transaction
Tx private key can be obtained using get_tx_key
command in hashmonkey-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": 5717,
"vin": [ {
"gen": {
"height": 5657
}
}
],
"vout": [ {
"amount": 34806844035018,
"target": {
"tagged_key": {
"key": "14a5b074eeade55e46e45499da8a52cc6e2bdd3197e9f138eda1a133718b9b54",
"view_tag": "e3"
}
}
}
],
"extra": [ 1, 94, 158, 236, 232, 214, 62, 83, 91, 33, 132, 132, 241, 149, 104, 101, 102, 224, 226, 139, 119, 17, 32, 60, 8, 224, 184, 59, 238, 237, 145, 180, 246, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}