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: a0722f92c54f40d0337145c4f432da76e340f1b69c835787a0f297eed68eda2e
Tx prefix hash: 00155cec316f8dcadb1795f458676c945f19e518a0960577e1c332a10d644236
Tx public key: 76eee30de68385c9d3a0a88299f40d1081816cc2fc14a0ba30cbbb83b1cf4b4d
| Timestamp: 1780071266 | Timestamp [UTC]: 2026-05-29 16:14:26 | Age [y:d:h:m:s]: 00:010:10:26:10 |
| Block: 4646 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3250 | RingCT/type: yes/0 |
| Extra: 0176eee30de68385c9d3a0a88299f40d1081816cc2fc14a0ba30cbbb83b1cf4b4d02090000000626697be300 | ||
1 output(s) for total of 34.874027917634 HMNY
| stealth address | amount | amount idx | tag |
| 00: 1e9d866c093076f05264a6b3ea145fb9ffa87bf80942ae7c15130d47f3042934 | 34.874027917634 | 5835 of 0 | <38> |
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": 4706,
"vin": [ {
"gen": {
"height": 4646
}
}
],
"vout": [ {
"amount": 34874027917634,
"target": {
"tagged_key": {
"key": "1e9d866c093076f05264a6b3ea145fb9ffa87bf80942ae7c15130d47f3042934",
"view_tag": "38"
}
}
}
],
"extra": [ 1, 118, 238, 227, 13, 230, 131, 133, 201, 211, 160, 168, 130, 153, 244, 13, 16, 129, 129, 108, 194, 252, 20, 160, 186, 48, 203, 187, 131, 177, 207, 75, 77, 2, 9, 0, 0, 0, 6, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}