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: a9ab757eb6b54753cac5d0aaa326f488de1c9095c7e14584e0ed15e068539efd
Tx prefix hash: 866e430e2b8c822190dd782fb78e7e90ff8d9169f3efb5d95e100b306fa1b467
Tx public key: a39e0818e48665106afa7ae9c2de5d728b242ed97b8516f031fe875f3a255802
| Timestamp: 1780742262 | Timestamp [UTC]: 2026-06-06 10:37:42 | Age [y:d:h:m:s]: 00:002:14:58:15 |
| Block: 6419 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1467 | RingCT/type: yes/0 |
| Extra: 01a39e0818e48665106afa7ae9c2de5d728b242ed97b8516f031fe875f3a255802020900000002e49593ff00 | ||
1 output(s) for total of 34.756292476292 HMNY
| stealth address | amount | amount idx | tag |
| 00: 4a47912151fdb328683eb0abb5b50c16a6d038414404d29f829caeca74a96489 | 34.756292476292 | 7910 of 0 | <79> |
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": 6479,
"vin": [ {
"gen": {
"height": 6419
}
}
],
"vout": [ {
"amount": 34756292476292,
"target": {
"tagged_key": {
"key": "4a47912151fdb328683eb0abb5b50c16a6d038414404d29f829caeca74a96489",
"view_tag": "79"
}
}
}
],
"extra": [ 1, 163, 158, 8, 24, 228, 134, 101, 16, 106, 250, 122, 233, 194, 222, 93, 114, 139, 36, 46, 217, 123, 133, 22, 240, 49, 254, 135, 95, 58, 37, 88, 2, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}