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: 8453c100d2099b3c7c84ac35a422368f6d3e86e79701c704c7309a4dce2fcc53
Tx prefix hash: f6c7e7a5acf4ba5f2f4db6e06d9f9b887d73a3cf6eb29165c70f5fcf8a0267e9
Tx public key: 11b6813db461b983bcde46d3a6ca000903bdb6c1fb76302e4cb844f55dc6adef
| Timestamp: 1780983419 | Timestamp [UTC]: 2026-06-09 05:36:59 | Age [y:d:h:m:s]: 00:000:04:33:04 |
| Block: 8089 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 334 | RingCT/type: yes/0 |
| Extra: 0111b6813db461b983bcde46d3a6ca000903bdb6c1fb76302e4cb844f55dc6adef020900000001e49593ff00 | ||
1 output(s) for total of 34.645760249168 HMNY
| stealth address | amount | amount idx | tag |
| 00: 9699f91312d73679358b169d47ba7242901710e31c85eafb3bb21f07b9b468ce | 34.645760249168 | 10021 of 0 | <a1> |
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": 8149,
"vin": [ {
"gen": {
"height": 8089
}
}
],
"vout": [ {
"amount": 34645760249168,
"target": {
"tagged_key": {
"key": "9699f91312d73679358b169d47ba7242901710e31c85eafb3bb21f07b9b468ce",
"view_tag": "a1"
}
}
}
],
"extra": [ 1, 17, 182, 129, 61, 180, 97, 185, 131, 188, 222, 70, 211, 166, 202, 0, 9, 3, 189, 182, 193, 251, 118, 48, 46, 76, 184, 68, 245, 93, 198, 173, 239, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}