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: 8e26e2078271c645114c36f56d46a5222426573f179373a74094bcb59ddbd8a9
Tx prefix hash: 8af6dfc3f1fe2137f1cd7a7de3454d36302dd70a75a12267df76d4d08de35542
Tx public key: 6f46444aa2fa3b2c65f38d61ac1a9b5b378d1cdd5aa7b293c98c12f78d02640c
| Timestamp: 1779908081 | Timestamp [UTC]: 2026-05-27 18:54:41 | Age [y:d:h:m:s]: 00:012:06:41:16 |
| Block: 3211 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4675 | RingCT/type: yes/0 |
| Extra: 016f46444aa2fa3b2c65f38d61ac1a9b5b378d1cdd5aa7b293c98c12f78d02640c02090000000126697be300 | ||
1 output(s) for total of 34.969610549903 HMNY
| stealth address | amount | amount idx | tag |
| 00: 2d32fafa1a16ccaebddd2fde7efa8dbb457a0439040b242c63c4a0bc8aa50183 | 34.969610549903 | 3849 of 0 | <ef> |
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": 3271,
"vin": [ {
"gen": {
"height": 3211
}
}
],
"vout": [ {
"amount": 34969610549903,
"target": {
"tagged_key": {
"key": "2d32fafa1a16ccaebddd2fde7efa8dbb457a0439040b242c63c4a0bc8aa50183",
"view_tag": "ef"
}
}
}
],
"extra": [ 1, 111, 70, 68, 74, 162, 250, 59, 44, 101, 243, 141, 97, 172, 26, 155, 91, 55, 141, 28, 221, 90, 167, 178, 147, 201, 140, 18, 247, 141, 2, 100, 12, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}