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: 3dcc441ce582bb2bd504bb32de1c82a60b5bc39e2337f68597739ecfad2f434c
Tx prefix hash: 884a0c2d9bcf86ffd91c3099100d42f5492da78ac45d5b9bbd65e424341cc392
Tx public key: 6b825a86decf2adf56e9fda40275cfa1726db1de3c328ef3155d9a06c81cd541
| Timestamp: 1779636576 | Timestamp [UTC]: 2026-05-24 15:29:36 | Age [y:d:h:m:s]: 00:015:09:17:11 |
| Block: 1126 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6760 | RingCT/type: yes/0 |
| Extra: 016b825a86decf2adf56e9fda40275cfa1726db1de3c328ef3155d9a06c81cd541020900000001ba6d17be00 | ||
1 output(s) for total of 35.108955487195 HMNY
| stealth address | amount | amount idx | tag |
| 00: fd860bdd5863ab237e5abc5f14a4d7df2c9e7eeb011d90c6de014309c22ae7ff | 35.108955487195 | 1268 of 0 | <37> |
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": 1186,
"vin": [ {
"gen": {
"height": 1126
}
}
],
"vout": [ {
"amount": 35108955487195,
"target": {
"tagged_key": {
"key": "fd860bdd5863ab237e5abc5f14a4d7df2c9e7eeb011d90c6de014309c22ae7ff",
"view_tag": "37"
}
}
}
],
"extra": [ 1, 107, 130, 90, 134, 222, 207, 42, 223, 86, 233, 253, 164, 2, 117, 207, 161, 114, 109, 177, 222, 60, 50, 142, 243, 21, 93, 154, 6, 200, 28, 213, 65, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}