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: e0777682113b45c541c1e3fbe9f406595d440ee03df96e9ef5e44f365ce6d38a
Tx prefix hash: 25a5476575989cc53ea21d254f958a42154b8f1a8b78d5da0dc9ac796bdbef3e
Tx public key: b915e6a708e6804947d411b434308ea1ab414e73b98f7a2c3985512ac402046d
| Timestamp: 1780802732 | Timestamp [UTC]: 2026-06-07 03:25:32 | Age [y:d:h:m:s]: 00:001:23:24:16 |
| Block: 6870 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1050 | RingCT/type: yes/0 |
| Extra: 01b915e6a708e6804947d411b434308ea1ab414e73b98f7a2c3985512ac402046d020900000001e49593ff00 | ||
1 output(s) for total of 34.726407445910 HMNY
| stealth address | amount | amount idx | tag |
| 00: 9e25d2710eb7accb5ebeb61331a0ca53adf5c25be46debdf25b4c2f3566b1bb0 | 34.726407445910 | 8480 of 0 | <d9> |
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": 6930,
"vin": [ {
"gen": {
"height": 6870
}
}
],
"vout": [ {
"amount": 34726407445910,
"target": {
"tagged_key": {
"key": "9e25d2710eb7accb5ebeb61331a0ca53adf5c25be46debdf25b4c2f3566b1bb0",
"view_tag": "d9"
}
}
}
],
"extra": [ 1, 185, 21, 230, 167, 8, 230, 128, 73, 71, 212, 17, 180, 52, 48, 142, 161, 171, 65, 78, 115, 185, 143, 122, 44, 57, 133, 81, 42, 196, 2, 4, 109, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}