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: 97559f1e2c20d5758a1c353c2d05bfe384c5ee27c99340798428c321fd6e57ed
Tx prefix hash: b5fc0178fee1f6ddc962315fecdf8bcef1c7791b88a9db185e1230c08d23b802
Tx public key: 651ba94fc25cb9b0853a2b03deaadab4a654e4c7c82c81eaa7e3f3948e7ae41d
| Timestamp: 1780046909 | Timestamp [UTC]: 2026-05-29 09:28:29 | Age [y:d:h:m:s]: 00:010:16:07:28 |
| Block: 4352 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3534 | RingCT/type: yes/0 |
| Extra: 01651ba94fc25cb9b0853a2b03deaadab4a654e4c7c82c81eaa7e3f3948e7ae41d02090000000126697be300 | ||
1 output(s) for total of 34.926520997694 HMNY
| stealth address | amount | amount idx | tag |
| 00: 8a7f464a807af0ff209ca6de33b12276285eeeddbef1e93649edf13c56ce2c74 | 34.926520997694 | 5440 of 0 | <53> |
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": 4412,
"vin": [ {
"gen": {
"height": 4352
}
}
],
"vout": [ {
"amount": 34926520997694,
"target": {
"tagged_key": {
"key": "8a7f464a807af0ff209ca6de33b12276285eeeddbef1e93649edf13c56ce2c74",
"view_tag": "53"
}
}
}
],
"extra": [ 1, 101, 27, 169, 79, 194, 92, 185, 176, 133, 58, 43, 3, 222, 170, 218, 180, 166, 84, 228, 199, 200, 44, 129, 234, 167, 227, 243, 148, 142, 122, 228, 29, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}