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: ff27f59d7a9541f23bff69c436a9dd294ca776e5917e34744274c72def3b1ad3
Tx prefix hash: ee5d785cb7b90f1c143e9cf6aadd569cc7e746b1a3825f2556dccfa15eca8229
Tx public key: cade5e75c472772b13cb7c50318ad3e27e1a3985caba3bf5e42c3aedbd34ee64
| Timestamp: 1779722612 | Timestamp [UTC]: 2026-05-25 15:23:32 | Age [y:d:h:m:s]: 00:014:09:23:15 |
| Block: 1782 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6104 | RingCT/type: yes/0 |
| Extra: 01cade5e75c472772b13cb7c50318ad3e27e1a3985caba3bf5e42c3aedbd34ee64020900000001ba6d17be00 | ||
1 output(s) for total of 35.065053864393 HMNY
| stealth address | amount | amount idx | tag |
| 00: 18711cea82df8f428b44be49ffcb210774cecead12818c902f9279fac0b190e9 | 35.065053864393 | 1969 of 0 | <8c> |
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": 1842,
"vin": [ {
"gen": {
"height": 1782
}
}
],
"vout": [ {
"amount": 35065053864393,
"target": {
"tagged_key": {
"key": "18711cea82df8f428b44be49ffcb210774cecead12818c902f9279fac0b190e9",
"view_tag": "8c"
}
}
}
],
"extra": [ 1, 202, 222, 94, 117, 196, 114, 119, 43, 19, 203, 124, 80, 49, 138, 211, 226, 126, 26, 57, 133, 202, 186, 59, 245, 228, 44, 58, 237, 189, 52, 238, 100, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}