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: 804da0534fbcaa1e737c0047624d151a67ddd3e8bc7a5c31ac3fbcb7ba2742f6
Tx prefix hash: 8e9a37626d12923c49f42798ebbde1aedb6c54266c8d3004d0e70c0964ce433c
Tx public key: 24e6b1e3258d3045705366054a0d50d21b71b4fc21b4b335dd706b0653239e2c
| Timestamp: 1779868209 | Timestamp [UTC]: 2026-05-27 07:50:09 | Age [y:d:h:m:s]: 00:012:17:45:48 |
| Block: 2771 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5115 | RingCT/type: yes/0 |
| Extra: 0124e6b1e3258d3045705366054a0d50d21b71b4fc21b4b335dd706b0653239e2c02090000000126697be300 | ||
1 output(s) for total of 35.006379361235 HMNY
| stealth address | amount | amount idx | tag |
| 00: 78326af5e45a86fbef8d66fa9f510b891067f2a94bb5f9c1fddeed8f043a9f93 | 35.006379361235 | 3275 of 0 | <bf> |
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": 2831,
"vin": [ {
"gen": {
"height": 2771
}
}
],
"vout": [ {
"amount": 35006379361235,
"target": {
"tagged_key": {
"key": "78326af5e45a86fbef8d66fa9f510b891067f2a94bb5f9c1fddeed8f043a9f93",
"view_tag": "bf"
}
}
}
],
"extra": [ 1, 36, 230, 177, 227, 37, 141, 48, 69, 112, 83, 102, 5, 74, 13, 80, 210, 27, 113, 180, 252, 33, 180, 179, 53, 221, 112, 107, 6, 83, 35, 158, 44, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}