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: ad6f9dc3230f616baf755b3f2dfa00be733381811d033d6077627b098357217d
Tx prefix hash: e716399a4538a7dc25110cf422ae3891b6a0a6b2e49c2bf03c6b55f99112cecf
Tx public key: 5010d67d079d86e3355c34509124622f1f55e5f863aef1e4a48aadb962bda204
| Timestamp: 1780991990 | Timestamp [UTC]: 2026-06-09 07:59:50 | Age [y:d:h:m:s]: 00:000:05:37:46 |
| Block: 8250 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 351 | RingCT/type: yes/0 |
| Extra: 015010d67d079d86e3355c34509124622f1f55e5f863aef1e4a48aadb962bda204020900000001e49593ff00 | ||
1 output(s) for total of 34.647355543911 HMNY
| stealth address | amount | amount idx | tag |
| 00: 0fa35b9d891381dc80c58bcfef176eddcf09f40fcfbccb0bcd181d35653de88e | 34.647355543911 | 10210 of 0 | <4e> |
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": 8310,
"vin": [ {
"gen": {
"height": 8250
}
}
],
"vout": [ {
"amount": 34647355543911,
"target": {
"tagged_key": {
"key": "0fa35b9d891381dc80c58bcfef176eddcf09f40fcfbccb0bcd181d35653de88e",
"view_tag": "4e"
}
}
}
],
"extra": [ 1, 80, 16, 214, 125, 7, 157, 134, 227, 53, 92, 52, 80, 145, 36, 98, 47, 31, 85, 229, 248, 99, 174, 241, 228, 164, 138, 173, 185, 98, 189, 162, 4, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}