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: c1b59d173c3670d84fad048546489b13daf1ac8e802dc445fcb3eb41c436c398
Tx prefix hash: de252a9df546da956ac62b94dc8fe2f08bcffb24ad4da0c4c4a8b2501bdcd4c9
Tx public key: e3c98cecd696c5c3e5c0eb27c3a9674f18c4fdf0eb281e720aa1da0e9147d2ac
| Timestamp: 1780803549 | Timestamp [UTC]: 2026-06-07 03:39:09 | Age [y:d:h:m:s]: 00:001:21:56:48 |
| Block: 6890 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 996 | RingCT/type: yes/0 |
| Extra: 01e3c98cecd696c5c3e5c0eb27c3a9674f18c4fdf0eb281e720aa1da0e9147d2ac020900000003e49593ff00 | ||
1 output(s) for total of 34.725082762598 HMNY
| stealth address | amount | amount idx | tag |
| 00: dc2895de3480041c8e6f2c046c812061bb0482bb237b86ebc035e8018c461d36 | 34.725082762598 | 8502 of 0 | <dc> |
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": 6950,
"vin": [ {
"gen": {
"height": 6890
}
}
],
"vout": [ {
"amount": 34725082762598,
"target": {
"tagged_key": {
"key": "dc2895de3480041c8e6f2c046c812061bb0482bb237b86ebc035e8018c461d36",
"view_tag": "dc"
}
}
}
],
"extra": [ 1, 227, 201, 140, 236, 214, 150, 197, 195, 229, 192, 235, 39, 195, 169, 103, 79, 24, 196, 253, 240, 235, 40, 30, 114, 10, 161, 218, 14, 145, 71, 210, 172, 2, 9, 0, 0, 0, 3, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}