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: bfe3517a6a3e4c9f3dc1dc174f864e22753a45c3be905c0e9bdc0be40d04ea06
Tx prefix hash: 4aac4e3c0dc019389d83a172a7d1aa4c0e1c92b2987e83305c3201c2b40d012b
Tx public key: 6d5f5dbca471c9f6636922c57d5e53d4c9f34adbb5056ea6259fc7dfe4736419
| Timestamp: 1781012942 | Timestamp [UTC]: 2026-06-09 13:49:02 | Age [y:d:h:m:s]: 00:007:19:14:55 |
| Block: 8603 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 142 | RingCT/type: yes/0 |
| Extra: 016d5f5dbca471c9f6636922c57d5e53d4c9f34adbb5056ea6259fc7dfe4736419020900000001e49593ff00 | ||
1 output(s) for total of 34.611810947740 HMNY
| stealth address | amount | amount idx | tag |
| 00: 65b98b6d163940d6fcb9e7adb5faf9ab363d3f634c698218db67a06f6d83ca8c | 34.611810947740 | 10631 of 0 | <a7> |
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": 8663,
"vin": [ {
"gen": {
"height": 8603
}
}
],
"vout": [ {
"amount": 34611810947740,
"target": {
"tagged_key": {
"key": "65b98b6d163940d6fcb9e7adb5faf9ab363d3f634c698218db67a06f6d83ca8c",
"view_tag": "a7"
}
}
}
],
"extra": [ 1, 109, 95, 93, 188, 164, 113, 201, 246, 99, 105, 34, 197, 125, 94, 83, 212, 201, 243, 74, 219, 181, 5, 110, 166, 37, 159, 199, 223, 228, 115, 100, 25, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}