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: a61e42d17449812a285199741da2e16f8e5053b10fe46cd7d7e027ed142605e0
Tx prefix hash: 2ae3e08a088394c190457a966be50fb07371b6292cb0dde973b75e5de2d4889d
Tx public key: a5ffcc0dbb09dc2f219ba0809c54e6467e5e76301748565da88a69d5e904dcbf
| Timestamp: 1779633241 | Timestamp [UTC]: 2026-05-24 14:34:01 | Age [y:d:h:m:s]: 00:015:11:01:56 |
| Block: 977 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6909 | RingCT/type: yes/0 |
| Extra: 01a5ffcc0dbb09dc2f219ba0809c54e6467e5e76301748565da88a69d5e904dcbf020900000002ba6d17be00 | ||
1 output(s) for total of 35.118934702385 HMNY
| stealth address | amount | amount idx | tag |
| 00: 42ca442119ee2b3c5caa5a6ff3ae1ddb05e8c3025b8e8a1fbee8f2b065ea633e | 35.118934702385 | 1113 of 0 | <98> |
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": 1037,
"vin": [ {
"gen": {
"height": 977
}
}
],
"vout": [ {
"amount": 35118934702385,
"target": {
"tagged_key": {
"key": "42ca442119ee2b3c5caa5a6ff3ae1ddb05e8c3025b8e8a1fbee8f2b065ea633e",
"view_tag": "98"
}
}
}
],
"extra": [ 1, 165, 255, 204, 13, 187, 9, 220, 47, 33, 155, 160, 128, 156, 84, 230, 70, 126, 94, 118, 48, 23, 72, 86, 93, 168, 138, 105, 213, 233, 4, 220, 191, 2, 9, 0, 0, 0, 2, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}