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: b5fe599cce7879c523bfeb022164bae9a7143881097f6edae63671efb60db27a
Tx prefix hash: 31a7d539300224f30f3de5b83b56ea9080de0175d23fe4ef475b556f4a5229d3
Tx public key: 042faab2657164ce6d5bae525277f7503afbb51d7eb7441eb540caff4d38299d
| Timestamp: 1780074099 | Timestamp [UTC]: 2026-05-29 17:01:39 | Age [y:d:h:m:s]: 00:010:08:34:18 |
| Block: 4680 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3206 | RingCT/type: yes/0 |
| Extra: 01042faab2657164ce6d5bae525277f7503afbb51d7eb7441eb540caff4d38299d02090000000426697be300 | ||
1 output(s) for total of 34.871766413205 HMNY
| stealth address | amount | amount idx | tag |
| 00: 8f6eed3cbc7c55e56b4546d5c424145a0e1b3dae87c74668f406fc5c231697dc | 34.871766413205 | 5880 of 0 | <8d> |
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": 4740,
"vin": [ {
"gen": {
"height": 4680
}
}
],
"vout": [ {
"amount": 34871766413205,
"target": {
"tagged_key": {
"key": "8f6eed3cbc7c55e56b4546d5c424145a0e1b3dae87c74668f406fc5c231697dc",
"view_tag": "8d"
}
}
}
],
"extra": [ 1, 4, 47, 170, 178, 101, 113, 100, 206, 109, 91, 174, 82, 82, 119, 247, 80, 58, 251, 181, 29, 126, 183, 68, 30, 181, 64, 202, 255, 77, 56, 41, 157, 2, 9, 0, 0, 0, 4, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}