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: 0716c51961c5f19a0143efb3981f64863190b3d3494c49106ef54ba7a3c50e0b
Tx prefix hash: b260eab8c8c1a50549ce7020b44e49ec5998f0ca8dd95497c20dcef538d29f4c
Tx public key: 36c1c13d8310acd72a5934b82746a1fe352b7bb3ff5466f6cfc4ef6688054fe3
| Timestamp: 1779635172 | Timestamp [UTC]: 2026-05-24 15:06:12 | Age [y:d:h:m:s]: 00:015:08:12:41 |
| Block: 1066 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6820 | RingCT/type: yes/0 |
| Extra: 0136c1c13d8310acd72a5934b82746a1fe352b7bb3ff5466f6cfc4ef6688054fe3020900000001ba6d17be00 | ||
1 output(s) for total of 35.112973622037 HMNY
| stealth address | amount | amount idx | tag |
| 00: 937d80bc1265fdff18f91d7f63cccdb7fa7de6792ee72ae33dcb502d3e2c2f67 | 35.112973622037 | 1204 of 0 | <4f> |
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": 1126,
"vin": [ {
"gen": {
"height": 1066
}
}
],
"vout": [ {
"amount": 35112973622037,
"target": {
"tagged_key": {
"key": "937d80bc1265fdff18f91d7f63cccdb7fa7de6792ee72ae33dcb502d3e2c2f67",
"view_tag": "4f"
}
}
}
],
"extra": [ 1, 54, 193, 193, 61, 131, 16, 172, 215, 42, 89, 52, 184, 39, 70, 161, 254, 53, 43, 123, 179, 255, 84, 102, 246, 207, 196, 239, 102, 136, 5, 79, 227, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}