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: 1cdd0a7cd03d77463149d47ed47f77f50fe408bd8d63d633a23c1db42d54a399
Tx prefix hash: 4b47bddd577ba1c7aef4181306cff67db9e0b24246fd4217ea906323a6eb2f0e
Tx public key: 1ee0ac39d615793dad1c46ba32ab552af80d4067f75a61d87769b7e57a5a288d
| Timestamp: 1779939661 | Timestamp [UTC]: 2026-05-28 03:41:01 | Age [y:d:h:m:s]: 00:011:23:57:49 |
| Block: 3473 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4473 | RingCT/type: yes/0 |
| Extra: 011ee0ac39d615793dad1c46ba32ab552af80d4067f75a61d87769b7e57a5a288d02090000000226697be300 | ||
1 output(s) for total of 34.952139698335 HMNY
| stealth address | amount | amount idx | tag |
| 00: e072daf576b0f3ba85b11bfb3ff7325cf22b774930f7ad5a423981481c3225b0 | 34.952139698335 | 4192 of 0 | <98> |
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": 3533,
"vin": [ {
"gen": {
"height": 3473
}
}
],
"vout": [ {
"amount": 34952139698335,
"target": {
"tagged_key": {
"key": "e072daf576b0f3ba85b11bfb3ff7325cf22b774930f7ad5a423981481c3225b0",
"view_tag": "98"
}
}
}
],
"extra": [ 1, 30, 224, 172, 57, 214, 21, 121, 61, 173, 28, 70, 186, 50, 171, 85, 42, 248, 13, 64, 103, 247, 90, 97, 216, 119, 105, 183, 229, 122, 90, 40, 141, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}