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: 60a949993db700a32c9b68088d581923ab7225dfbd5c402b0708465776c32137
Tx prefix hash: 3cb04da70b59831ba1a56c87983930ab98b1a024526e66dfbc365042b9193abf
Tx public key: e45a8c006311385fa1e02bd32dea0509963a81960b0e4a7c775c1313f46d9276
| Timestamp: 1780687212 | Timestamp [UTC]: 2026-06-05 19:20:12 | Age [y:d:h:m:s]: 00:003:07:29:36 |
| Block: 5468 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2441 | RingCT/type: yes/0 |
| Extra: 01e45a8c006311385fa1e02bd32dea0509963a81960b0e4a7c775c1313f46d9276020900000001e49593ff00 | ||
1 output(s) for total of 34.819393789500 HMNY
| stealth address | amount | amount idx | tag |
| 00: 686ef471c7842291104ad99cc70b3d5ccb09a6f71db86f6ca79765ed88a890d7 | 34.819393789500 | 6907 of 0 | <1b> |
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": 5528,
"vin": [ {
"gen": {
"height": 5468
}
}
],
"vout": [ {
"amount": 34819393789500,
"target": {
"tagged_key": {
"key": "686ef471c7842291104ad99cc70b3d5ccb09a6f71db86f6ca79765ed88a890d7",
"view_tag": "1b"
}
}
}
],
"extra": [ 1, 228, 90, 140, 0, 99, 17, 56, 95, 161, 224, 43, 211, 45, 234, 5, 9, 150, 58, 129, 150, 11, 14, 74, 124, 119, 92, 19, 19, 244, 109, 146, 118, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}