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: 34a0f7ecf653bda65c81965d0a972ed6a1f07cabc5efaaad26d2de6fe92d46a6
Tx prefix hash: ef1a956db97fe2cce354b04e51accadd35c523ba07e30d9efcf6acceb96c5365
Tx public key: 414e6ae1b2e4355522c44ba50be4dcb2159987b8e1920fd4fdae6195db6fefa4
| Timestamp: 1781009745 | Timestamp [UTC]: 2026-06-09 12:55:45 | Age [y:d:h:m:s]: 00:007:20:19:21 |
| Block: 8580 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 165 | RingCT/type: yes/0 |
| Extra: 01414e6ae1b2e4355522c44ba50be4dcb2159987b8e1920fd4fdae6195db6fefa4020900000009e49593ff00 | ||
1 output(s) for total of 34.613329368671 HMNY
| stealth address | amount | amount idx | tag |
| 00: 765c038ad3cc107267c0e5bfbd3784ce09104a5665ec8ea36be95747631720b4 | 34.613329368671 | 10600 of 0 | <21> |
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": 8640,
"vin": [ {
"gen": {
"height": 8580
}
}
],
"vout": [ {
"amount": 34613329368671,
"target": {
"tagged_key": {
"key": "765c038ad3cc107267c0e5bfbd3784ce09104a5665ec8ea36be95747631720b4",
"view_tag": "21"
}
}
}
],
"extra": [ 1, 65, 78, 106, 225, 178, 228, 53, 85, 34, 196, 75, 165, 11, 228, 220, 178, 21, 153, 135, 184, 225, 146, 15, 212, 253, 174, 97, 149, 219, 111, 239, 164, 2, 9, 0, 0, 0, 9, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}