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: 503338eacbb5e074ff33dc183ebe7bf9e02665f68d81fd519019cf5a24a049d5
Tx prefix hash: 5fe0f724c693655fb7e2de636fdf026937ad71c397d9e0c52e3c48fa86ec1454
Tx public key: edf32a016a7db3fa7cc535e345c82f9674e35ed2b4fc8d8cca4fb0274031ccc1
| Timestamp: 1779472571 | Timestamp [UTC]: 2026-05-22 17:56:11 | Age [y:d:h:m:s]: 00:017:08:44:25 |
| Block: 579 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7317 | RingCT/type: yes/0 |
| Extra: 01edf32a016a7db3fa7cc535e345c82f9674e35ed2b4fc8d8cca4fb0274031ccc102090000000293369e7d00 | ||
1 output(s) for total of 35.145604502123 HMNY
| stealth address | amount | amount idx | tag |
| 00: e5534e2527cc2526a49f354f2f52d090a7253ee40e09fc9e64840b6a4283b4a3 | 35.145604502123 | 591 of 0 | <53> |
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": 639,
"vin": [ {
"gen": {
"height": 579
}
}
],
"vout": [ {
"amount": 35145604502123,
"target": {
"tagged_key": {
"key": "e5534e2527cc2526a49f354f2f52d090a7253ee40e09fc9e64840b6a4283b4a3",
"view_tag": "53"
}
}
}
],
"extra": [ 1, 237, 243, 42, 1, 106, 125, 179, 250, 124, 197, 53, 227, 69, 200, 47, 150, 116, 227, 94, 210, 180, 252, 141, 140, 202, 79, 176, 39, 64, 49, 204, 193, 2, 9, 0, 0, 0, 2, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}