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: 32c8fdc2a89b0e907492a0def3b2602cdae0868e725ff2ca80e1fc834bc8ed62
Tx prefix hash: f8a0a9b861cd731637521a464c96680cf547616e04364312772a87ec1f0ec989
Tx public key: 91c55718314c3b85defab8913e18a5e3b7c64c2941f44cd1e1757a05a37ab50f
| Timestamp: 1779879900 | Timestamp [UTC]: 2026-05-27 11:05:00 | Age [y:d:h:m:s]: 00:012:14:30:57 |
| Block: 2930 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4956 | RingCT/type: yes/0 |
| Extra: 0191c55718314c3b85defab8913e18a5e3b7c64c2941f44cd1e1757a05a37ab50f02090000000126697be300 | ||
1 output(s) for total of 34.988358077466 HMNY
| stealth address | amount | amount idx | tag |
| 00: 370820dd8edfc277852a64378a7ed88c315f85002480fdd22566be6093d2c710 | 34.988358077466 | 3474 of 0 | <08> |
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": 2990,
"vin": [ {
"gen": {
"height": 2930
}
}
],
"vout": [ {
"amount": 34988358077466,
"target": {
"tagged_key": {
"key": "370820dd8edfc277852a64378a7ed88c315f85002480fdd22566be6093d2c710",
"view_tag": "08"
}
}
}
],
"extra": [ 1, 145, 197, 87, 24, 49, 76, 59, 133, 222, 250, 184, 145, 62, 24, 165, 227, 183, 198, 76, 41, 65, 244, 76, 209, 225, 117, 122, 5, 163, 122, 181, 15, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}