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: 2e0acf564e7f56923125e4366c41f27830506801085a498d1d4b8bc541c45582
Tx prefix hash: 1c9d12a1c5b06ae649d267b016b377b4b6dde0f65a336916f0420984b7beab3e
Tx public key: 5291b6a629d849f4e36247ad9d1b332a3d75e3633e20f56c1f9debd43e3fa3ac
| Timestamp: 1780690899 | Timestamp [UTC]: 2026-06-05 20:21:39 | Age [y:d:h:m:s]: 00:003:07:29:19 |
| Block: 5695 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2270 | RingCT/type: yes/0 |
| Extra: 015291b6a629d849f4e36247ad9d1b332a3d75e3633e20f56c1f9debd43e3fa3ac020900000001e49593ff00 | ||
1 output(s) for total of 34.804321350152 HMNY
| stealth address | amount | amount idx | tag |
| 00: e39f8a53612e6ddb3d5307d064e0419204ff9e2e5a50fb65432e4089de2572bd | 34.804321350152 | 7146 of 0 | <95> |
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": 5755,
"vin": [ {
"gen": {
"height": 5695
}
}
],
"vout": [ {
"amount": 34804321350152,
"target": {
"tagged_key": {
"key": "e39f8a53612e6ddb3d5307d064e0419204ff9e2e5a50fb65432e4089de2572bd",
"view_tag": "95"
}
}
}
],
"extra": [ 1, 82, 145, 182, 166, 41, 216, 73, 244, 227, 98, 71, 173, 157, 27, 51, 42, 61, 117, 227, 99, 62, 32, 245, 108, 31, 157, 235, 212, 62, 63, 163, 172, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}