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: 22254931b388fed02408e367dc8d84a0fc0eaacf5fb519069e33a6a6e36dded1
Tx prefix hash: 1eb9bcf847285592455c5e85e0c6867746de9f4b572c497802882d42fde7e582
Tx public key: 94871283ad9c3062c1099d8c06aad04b48fb6389466751b47fa4287ff7e864b1
| Timestamp: 1780686295 | Timestamp [UTC]: 2026-06-05 19:04:55 | Age [y:d:h:m:s]: 00:009:13:14:40 |
| Block: 5418 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3327 | RingCT/type: yes/0 |
| Extra: 0194871283ad9c3062c1099d8c06aad04b48fb6389466751b47fa4287ff7e864b1020900000001e49593ff00 | ||
1 output(s) for total of 34.822714587170 HMNY
| stealth address | amount | amount idx | tag |
| 00: 6ac05087f7bd1d3e8781c8e1aecf4f0f468eb49704d3f1f982c820ed2297612f | 34.822714587170 | 6855 of 0 | <c5> |
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": 5478,
"vin": [ {
"gen": {
"height": 5418
}
}
],
"vout": [ {
"amount": 34822714587170,
"target": {
"tagged_key": {
"key": "6ac05087f7bd1d3e8781c8e1aecf4f0f468eb49704d3f1f982c820ed2297612f",
"view_tag": "c5"
}
}
}
],
"extra": [ 1, 148, 135, 18, 131, 173, 156, 48, 98, 193, 9, 157, 140, 6, 170, 208, 75, 72, 251, 99, 137, 70, 103, 81, 180, 127, 164, 40, 127, 247, 232, 100, 177, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}