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: adc745e9c5e8e3d4def688d3034ccb67f1a059c7ea108338a4787f5577c06f3c
Tx prefix hash: a5de5392b2f169a5beac908dbfaf759bba8657d9e1db2749760b6010aa5d98ab
Tx public key: 120403638c06a7cb7a50f8a43c38d50919f3ed08e7f36f62002c6b8578b5c210
| Timestamp: 1780801244 | Timestamp [UTC]: 2026-06-07 03:00:44 | Age [y:d:h:m:s]: 00:002:00:38:06 |
| Block: 6840 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1102 | RingCT/type: yes/0 |
| Extra: 01120403638c06a7cb7a50f8a43c38d50919f3ed08e7f36f62002c6b8578b5c210020900000001e49593ff00 | ||
1 output(s) for total of 34.728394565630 HMNY
| stealth address | amount | amount idx | tag |
| 00: 86ec9d43abf6aece609557d221d24b67a1e2c272681c927e14f803cf61ce9956 | 34.728394565630 | 8446 of 0 | <33> |
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": 6900,
"vin": [ {
"gen": {
"height": 6840
}
}
],
"vout": [ {
"amount": 34728394565630,
"target": {
"tagged_key": {
"key": "86ec9d43abf6aece609557d221d24b67a1e2c272681c927e14f803cf61ce9956",
"view_tag": "33"
}
}
}
],
"extra": [ 1, 18, 4, 3, 99, 140, 6, 167, 203, 122, 80, 248, 164, 60, 56, 213, 9, 25, 243, 237, 8, 231, 243, 111, 98, 0, 44, 107, 133, 120, 181, 194, 16, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}