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: a8e02a851eb911c415457d6f92f8bd7ea1f131e534f40df3d48b6e969e89ae2a
Tx prefix hash: bf0831915aa1d78239b6e984bf158934f78154ca78baf9e204056610db9a15a5
Tx public key: 0e56d3cc1aaf48aefbda4b53ce96430b1c019df90d484e1d6a680151f2b578c6
| Timestamp: 1780905935 | Timestamp [UTC]: 2026-06-08 08:05:35 | Age [y:d:h:m:s]: 00:000:12:02:36 |
| Block: 7866 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 20 | RingCT/type: yes/0 |
| Extra: 010e56d3cc1aaf48aefbda4b53ce96430b1c019df90d484e1d6a680151f2b578c60209000000014a728a4c00 | ||
1 output(s) for total of 34.660499581795 HMNY
| stealth address | amount | amount idx | tag |
| 00: a84d586e6d00b318a201a157ed30ca2f6c14effd27b4582187b4e0a6fe8445d2 | 34.660499581795 | 9752 of 0 | <c8> |
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": 7926,
"vin": [ {
"gen": {
"height": 7866
}
}
],
"vout": [ {
"amount": 34660499581795,
"target": {
"tagged_key": {
"key": "a84d586e6d00b318a201a157ed30ca2f6c14effd27b4582187b4e0a6fe8445d2",
"view_tag": "c8"
}
}
}
],
"extra": [ 1, 14, 86, 211, 204, 26, 175, 72, 174, 251, 218, 75, 83, 206, 150, 67, 11, 28, 1, 157, 249, 13, 72, 78, 29, 106, 104, 1, 81, 242, 181, 120, 198, 2, 9, 0, 0, 0, 1, 74, 114, 138, 76, 0
],
"rct_signatures": {
"type": 0
}
}