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: db7d3f16baaeb4cb39d7ab5ae18ca792efdfd497ab33f7332779568b832ba0b5
Tx prefix hash: afbf19b5f3eb011608c7e45622b6252371ad1ad149c14a2a989cf9a8ad440f8b
Tx public key: 3c92421745fe8acc32a3390ea52208f763919e1e53762773c9cc91753f4e275d
| Timestamp: 1780993127 | Timestamp [UTC]: 2026-06-09 08:18:47 | Age [y:d:h:m:s]: 00:000:08:33:09 |
| Block: 8271 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 451 | RingCT/type: yes/0 |
| Extra: 013c92421745fe8acc32a3390ea52208f763919e1e53762773c9cc91753f4e275d020900000002e49593ff00 | ||
1 output(s) for total of 34.633735484037 HMNY
| stealth address | amount | amount idx | tag |
| 00: 0e70b6ffd1609a32559d7202814b7a39d9312e02702a9df92a4ed49239fec2a0 | 34.633735484037 | 10235 of 0 | <66> |
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": 8331,
"vin": [ {
"gen": {
"height": 8271
}
}
],
"vout": [ {
"amount": 34633735484037,
"target": {
"tagged_key": {
"key": "0e70b6ffd1609a32559d7202814b7a39d9312e02702a9df92a4ed49239fec2a0",
"view_tag": "66"
}
}
}
],
"extra": [ 1, 60, 146, 66, 23, 69, 254, 138, 204, 50, 163, 57, 14, 165, 34, 8, 247, 99, 145, 158, 30, 83, 118, 39, 115, 201, 204, 145, 117, 63, 78, 39, 93, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}