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: f0072b134962c040ec36dda81ecd0602de2de375836b4e557d1b9e968b97e2dc
Tx prefix hash: 4b5595c305b35e3d66d50d0ee2199b7fa227df6db24f6cb53acd07695c3fd71a
Tx public key: 0100fbc3b4e49c0e4050e3c4e5d13bdfca8453b3712751b5393f3de92405691e
| Timestamp: 1779472199 | Timestamp [UTC]: 2026-05-22 17:49:59 | Age [y:d:h:m:s]: 00:017:10:00:59 |
| Block: 575 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7406 | RingCT/type: yes/0 |
| Extra: 010100fbc3b4e49c0e4050e3c4e5d13bdfca8453b3712751b5393f3de92405691e02090000000293369e7d00 | ||
1 output(s) for total of 35.145872643084 HMNY
| stealth address | amount | amount idx | tag |
| 00: 567b11b1c0c956f33da78bcda9ebaefe22f3e60bc84ee66d044f506be9c78afd | 35.145872643084 | 585 of 0 | <f3> |
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": 635,
"vin": [ {
"gen": {
"height": 575
}
}
],
"vout": [ {
"amount": 35145872643084,
"target": {
"tagged_key": {
"key": "567b11b1c0c956f33da78bcda9ebaefe22f3e60bc84ee66d044f506be9c78afd",
"view_tag": "f3"
}
}
}
],
"extra": [ 1, 1, 0, 251, 195, 180, 228, 156, 14, 64, 80, 227, 196, 229, 209, 59, 223, 202, 132, 83, 179, 113, 39, 81, 181, 57, 63, 61, 233, 36, 5, 105, 30, 2, 9, 0, 0, 0, 2, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}