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: 907d3c03dc505e0719eb6b9ec48ca668a751a38dcfa86b60cd521fce4da31f3f
Tx prefix hash: cc7de40351907e81fdd5c403fb67ebe7b58451ad65fdec7f271e3fe87b760c19
Tx public key: 71dab93d17b5e8cee2ab8a2645815f94737278ef041119c33a39712c2c2279ad
| Timestamp: 1780072163 | Timestamp [UTC]: 2026-05-29 16:29:23 | Age [y:d:h:m:s]: 00:011:00:39:40 |
| Block: 4653 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4081 | RingCT/type: yes/0 |
| Extra: 0171dab93d17b5e8cee2ab8a2645815f94737278ef041119c33a39712c2c2279ad02090000000126697be300 | ||
1 output(s) for total of 34.878581901792 HMNY
| stealth address | amount | amount idx | tag |
| 00: 100b1351e3204f8f56b93082d623a1d4f6fa1951383018185cbdb0cae97eb1e6 | 34.878581901792 | 5844 of 0 | <6e> |
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": 4713,
"vin": [ {
"gen": {
"height": 4653
}
}
],
"vout": [ {
"amount": 34878581901792,
"target": {
"tagged_key": {
"key": "100b1351e3204f8f56b93082d623a1d4f6fa1951383018185cbdb0cae97eb1e6",
"view_tag": "6e"
}
}
}
],
"extra": [ 1, 113, 218, 185, 61, 23, 181, 232, 206, 226, 171, 138, 38, 69, 129, 95, 148, 115, 114, 120, 239, 4, 17, 25, 195, 58, 57, 113, 44, 44, 34, 121, 173, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}