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: 160f99cd0e5dbfd437402cf20ad311a6cff248b38649171210cc6dd7a09c7000
Tx prefix hash: 272508bd3818cfcb18b8e81c7d5bfccf290fde9090062f0ec092d54c61cb1519
Tx public key: 2a8316dbc67b550d5dd70ee6b71805ed0c5ad620e4e08b8d482f94af0458d9c7
| Timestamp: 1780313009 | Timestamp [UTC]: 2026-06-01 11:23:29 | Age [y:d:h:m:s]: 00:007:14:12:28 |
| Block: 4984 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2902 | RingCT/type: yes/0 |
| Extra: 012a8316dbc67b550d5dd70ee6b71805ed0c5ad620e4e08b8d482f94af0458d9c702090000000326697be300 | ||
1 output(s) for total of 34.851552419613 HMNY
| stealth address | amount | amount idx | tag |
| 00: d7ae8688071ff72ebdecbea559969b9b8dff64317d9574caf62e725d7e7a43f2 | 34.851552419613 | 6345 of 0 | <d7> |
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": 5044,
"vin": [ {
"gen": {
"height": 4984
}
}
],
"vout": [ {
"amount": 34851552419613,
"target": {
"tagged_key": {
"key": "d7ae8688071ff72ebdecbea559969b9b8dff64317d9574caf62e725d7e7a43f2",
"view_tag": "d7"
}
}
}
],
"extra": [ 1, 42, 131, 22, 219, 198, 123, 85, 13, 93, 215, 14, 230, 183, 24, 5, 237, 12, 90, 214, 32, 228, 224, 139, 141, 72, 47, 148, 175, 4, 88, 217, 199, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}