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: a7b9e6be1c694b09cd6a87095d14ea9d334c1055f65fd59afbb36da3ac2d6e55
Tx prefix hash: 720649b293e76f33913bed585b8d2f7afe86304fb2b9537230f63f080c6e82c3
Tx public key: 0dea6c5fc8fb0ebec97f7ae714e70f209d0cd979e8a764a70a6ee37e4eee541b
| Timestamp: 1780076174 | Timestamp [UTC]: 2026-05-29 17:36:14 | Age [y:d:h:m:s]: 00:010:07:59:43 |
| Block: 4704 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3182 | RingCT/type: yes/0 |
| Extra: 010dea6c5fc8fb0ebec97f7ae714e70f209d0cd979e8a764a70a6ee37e4eee541b02090000000326697be300 | ||
1 output(s) for total of 34.870170145435 HMNY
| stealth address | amount | amount idx | tag |
| 00: ba19ec59f8fddd3690153a7512a48106a066785f9bd39bec3ea73af92c49e476 | 34.870170145435 | 5910 of 0 | <9c> |
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": 4764,
"vin": [ {
"gen": {
"height": 4704
}
}
],
"vout": [ {
"amount": 34870170145435,
"target": {
"tagged_key": {
"key": "ba19ec59f8fddd3690153a7512a48106a066785f9bd39bec3ea73af92c49e476",
"view_tag": "9c"
}
}
}
],
"extra": [ 1, 13, 234, 108, 95, 200, 251, 14, 190, 201, 127, 122, 231, 20, 231, 15, 32, 157, 12, 217, 121, 232, 167, 100, 167, 10, 110, 227, 126, 78, 238, 84, 27, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}