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: d85eb43c27e60d81d23b7a2ea5d4384a44ecdca5893dc5a12d2a245c4688abbc
Tx prefix hash: db7414a3578413bb4d85f271d8ef89ea9c6c150f7fdcd4fe3f34b39c5524a36e
Tx public key: 1afe019aa7c7268c58c6242cff3c8b6fd861544fb0f257dcac6728f618d28f19
| Timestamp: 1780984196 | Timestamp [UTC]: 2026-06-09 05:49:56 | Age [y:d:h:m:s]: 00:000:10:09:48 |
| Block: 8108 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 583 | RingCT/type: yes/0 |
| Extra: 011afe019aa7c7268c58c6242cff3c8b6fd861544fb0f257dcac6728f618d28f19020900000001e49593ff00 | ||
1 output(s) for total of 34.644504721395 HMNY
| stealth address | amount | amount idx | tag |
| 00: 5947517a2c08e75b02bffae64f25160e6f7e683b09c68fb396b632e1098f5731 | 34.644504721395 | 10044 of 0 | <3b> |
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": 8168,
"vin": [ {
"gen": {
"height": 8108
}
}
],
"vout": [ {
"amount": 34644504721395,
"target": {
"tagged_key": {
"key": "5947517a2c08e75b02bffae64f25160e6f7e683b09c68fb396b632e1098f5731",
"view_tag": "3b"
}
}
}
],
"extra": [ 1, 26, 254, 1, 154, 167, 199, 38, 140, 88, 198, 36, 44, 255, 60, 139, 111, 216, 97, 84, 79, 176, 242, 87, 220, 172, 103, 40, 246, 24, 210, 143, 25, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}