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: 5f3e69b0be765e1826046c908a55c499a9f0e911e1e8bac9117e310eb79d2a45
Tx prefix hash: cd0839fb305904e0b8bfb814e76b883eb9a2c50e810947b99a1edb214578e6f2
Tx public key: ba4bd448ad32815ae3a8914c509c0e4c281d09a754e12ddd4b4d5d6d94baa71f
| Timestamp: 1779435856 | Timestamp [UTC]: 2026-05-22 07:44:16 | Age [y:d:h:m:s]: 00:017:17:02:31 |
| Block: 130 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7756 | RingCT/type: yes/0 |
| Extra: 01ba4bd448ad32815ae3a8914c509c0e4c281d09a754e12ddd4b4d5d6d94baa71f020900000001a662ed0300 | ||
1 output(s) for total of 35.175716102172 HMNY
| stealth address | amount | amount idx | tag |
| 00: 3c571d6ac4e18a3bdddb5ecf46e4192f3e8bd1d1871c5829f93d0aa5fe6748cd | 35.175716102172 | 126 of 0 | <b4> |
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": 190,
"vin": [ {
"gen": {
"height": 130
}
}
],
"vout": [ {
"amount": 35175716102172,
"target": {
"tagged_key": {
"key": "3c571d6ac4e18a3bdddb5ecf46e4192f3e8bd1d1871c5829f93d0aa5fe6748cd",
"view_tag": "b4"
}
}
}
],
"extra": [ 1, 186, 75, 212, 72, 173, 50, 129, 90, 227, 168, 145, 76, 80, 156, 14, 76, 40, 29, 9, 167, 84, 225, 45, 221, 75, 77, 93, 109, 148, 186, 167, 31, 2, 9, 0, 0, 0, 1, 166, 98, 237, 3, 0
],
"rct_signatures": {
"type": 0
}
}