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: e257e9df40c2bb561b8536a9a9d4c215d4f64225aad2ce3e573cf655a3710c38
Tx prefix hash: 7a931b9c8707c6becf45f3d2bd05e14565b29d8211efbe4820bd036f8d973f6f
Tx public key: fad153b559f98f268dfb4f5bc9c637dfceece4d3cf3251b9cc3a3f7253bfb257
| Timestamp: 1780024371 | Timestamp [UTC]: 2026-05-29 03:12:51 | Age [y:d:h:m:s]: 00:019:05:16:21 |
| Block: 4163 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4582 | RingCT/type: yes/0 |
| Extra: 01fad153b559f98f268dfb4f5bc9c637dfceece4d3cf3251b9cc3a3f7253bfb25702090000000526697be300 | ||
1 output(s) for total of 34.906170428583 HMNY
| stealth address | amount | amount idx | tag |
| 00: d954ef77e4dfbda4eaab20ffa0ef565913d365ad61e8535467f393b6a7905a93 | 34.906170428583 | 5194 of 0 | <f0> |
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": 4223,
"vin": [ {
"gen": {
"height": 4163
}
}
],
"vout": [ {
"amount": 34906170428583,
"target": {
"tagged_key": {
"key": "d954ef77e4dfbda4eaab20ffa0ef565913d365ad61e8535467f393b6a7905a93",
"view_tag": "f0"
}
}
}
],
"extra": [ 1, 250, 209, 83, 181, 89, 249, 143, 38, 141, 251, 79, 91, 201, 198, 55, 223, 206, 236, 228, 211, 207, 50, 81, 185, 204, 58, 63, 114, 83, 191, 178, 87, 2, 9, 0, 0, 0, 5, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}