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: 7a34de1efa861637d498114ac90997f46a6eacf064308f20959e0b7ecd39bed1
Tx prefix hash: c2470fd3c5e9fd7c5d18455fe81bf922dfdb466bfe4de08625652ddc51c114df
Tx public key: 42602c59d0a13a6465962849de06c61cc62548a2b17d8de306189a0a8cc090e8
| Timestamp: 1781016379 | Timestamp [UTC]: 2026-06-09 14:46:19 | Age [y:d:h:m:s]: 00:003:20:15:57 |
| Block: 8637 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 108 | RingCT/type: yes/0 |
| Extra: 0142602c59d0a13a6465962849de06c61cc62548a2b17d8de306189a0a8cc090e8020900000001e49593ff00 | ||
1 output(s) for total of 34.609566447509 HMNY
| stealth address | amount | amount idx | tag |
| 00: 3673605a259244f7c418cbe11b053c2f7fc056bb8870d7c433e31d75d6e73908 | 34.609566447509 | 10677 of 0 | <f1> |
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": 8697,
"vin": [ {
"gen": {
"height": 8637
}
}
],
"vout": [ {
"amount": 34609566447509,
"target": {
"tagged_key": {
"key": "3673605a259244f7c418cbe11b053c2f7fc056bb8870d7c433e31d75d6e73908",
"view_tag": "f1"
}
}
}
],
"extra": [ 1, 66, 96, 44, 89, 208, 161, 58, 100, 101, 150, 40, 73, 222, 6, 198, 28, 198, 37, 72, 162, 177, 125, 141, 227, 6, 24, 154, 10, 140, 192, 144, 232, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}