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: 1ea9c6ac2f3e9caa01380b3f97a0a263fd7ed031d3053e4b56418db05bec827f
Tx prefix hash: b0879686f3fe114d09443da631ecf8e3d419843b4e89a34df721cd51e58bd566
Tx public key: 48ddc0b35ad8013ffdef378483148b236fd25d0444c1b5599a95200aa5f245a1
| Timestamp: 1781020466 | Timestamp [UTC]: 2026-06-09 15:54:26 | Age [y:d:h:m:s]: 00:007:19:17:16 |
| Block: 8684 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 61 | RingCT/type: yes/0 |
| Extra: 0148ddc0b35ad8013ffdef378483148b236fd25d0444c1b5599a95200aa5f245a1020900000003e49593ff00 | ||
1 output(s) for total of 34.606463995678 HMNY
| stealth address | amount | amount idx | tag |
| 00: 2842ab8a16ce9ab6bb6d6fe0b66d34478c96fcc91438d6aed19d1c9d0ef34cce | 34.606463995678 | 10738 of 0 | <cd> |
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": 8744,
"vin": [ {
"gen": {
"height": 8684
}
}
],
"vout": [ {
"amount": 34606463995678,
"target": {
"tagged_key": {
"key": "2842ab8a16ce9ab6bb6d6fe0b66d34478c96fcc91438d6aed19d1c9d0ef34cce",
"view_tag": "cd"
}
}
}
],
"extra": [ 1, 72, 221, 192, 179, 90, 216, 1, 63, 253, 239, 55, 132, 131, 20, 139, 35, 111, 210, 93, 4, 68, 193, 181, 89, 154, 149, 32, 10, 165, 242, 69, 161, 2, 9, 0, 0, 0, 3, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}