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: fad7ba369621efb1edcfaef9e2ad5d01cef7e513cca0ad3b60e158c4be9cee71
Tx prefix hash: 3a3e2e78840e877918095c6c90bf7c3fb0b2db5cc1e34bb6cb09048da12b8b34
Tx public key: d5954aa430822731db16e4c70500a7255d9b1b8d14901d2020880582341cec97
| Timestamp: 1780047314 | Timestamp [UTC]: 2026-05-29 09:35:14 | Age [y:d:h:m:s]: 00:015:05:36:16 |
| Block: 4359 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4386 | RingCT/type: yes/0 |
| Extra: 01d5954aa430822731db16e4c70500a7255d9b1b8d14901d2020880582341cec9702090000000126697be300 | ||
1 output(s) for total of 34.893123520679 HMNY
| stealth address | amount | amount idx | tag |
| 00: 8807bf5d2495e5852607115d9f8fb174eb69ae0e8faa9688776f509ea96e3f44 | 34.893123520679 | 5450 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": 4419,
"vin": [ {
"gen": {
"height": 4359
}
}
],
"vout": [ {
"amount": 34893123520679,
"target": {
"tagged_key": {
"key": "8807bf5d2495e5852607115d9f8fb174eb69ae0e8faa9688776f509ea96e3f44",
"view_tag": "dc"
}
}
}
],
"extra": [ 1, 213, 149, 74, 164, 48, 130, 39, 49, 219, 22, 228, 199, 5, 0, 167, 37, 93, 155, 27, 141, 20, 144, 29, 32, 32, 136, 5, 130, 52, 28, 236, 151, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}