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: 78792c4e52909ce32edcaddef1e54af4dd8aff71803f5c43e99d659bf57c6d61
Tx prefix hash: 54ab6d7c1427895d875c786c741763528cb5a16438a387717c916306a0c6604b
Tx public key: 30ae3cbbeee7575bd3b62ff32a1390ba20c08d7536d8c2d5304186c534d627a0
| Timestamp: 1780050396 | Timestamp [UTC]: 2026-05-29 10:26:36 | Age [y:d:h:m:s]: 00:015:00:35:40 |
| Block: 4389 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4356 | RingCT/type: yes/0 |
| Extra: 0130ae3cbbeee7575bd3b62ff32a1390ba20c08d7536d8c2d5304186c534d627a002090000001426697be300 | ||
1 output(s) for total of 34.891126975354 HMNY
| stealth address | amount | amount idx | tag |
| 00: 2d6fcbe8646b0438d13cbf9c22ab47889a032f0160072c02389315f5e382e93f | 34.891126975354 | 5490 of 0 | <e0> |
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": 4449,
"vin": [ {
"gen": {
"height": 4389
}
}
],
"vout": [ {
"amount": 34891126975354,
"target": {
"tagged_key": {
"key": "2d6fcbe8646b0438d13cbf9c22ab47889a032f0160072c02389315f5e382e93f",
"view_tag": "e0"
}
}
}
],
"extra": [ 1, 48, 174, 60, 187, 238, 231, 87, 91, 211, 182, 47, 243, 42, 19, 144, 186, 32, 192, 141, 117, 54, 216, 194, 213, 48, 65, 134, 197, 52, 214, 39, 160, 2, 9, 0, 0, 0, 20, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}