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: d8b51b02472f28743bd685da8453f1a4998e5d12f1e7b7982772a9f53ddd56f2
Tx prefix hash: dd6e218ed472afa4408466a94168e6acc2844c3064e7b43e0b81118803266bb1
Tx public key: 1c72722992c96d711af3c2f5c7003261fd7434193a8802222e51a32630ae6aaf
| Timestamp: 1779645945 | Timestamp [UTC]: 2026-05-24 18:05:45 | Age [y:d:h:m:s]: 00:015:07:30:12 |
| Block: 1453 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6433 | RingCT/type: yes/0 |
| Extra: 011c72722992c96d711af3c2f5c7003261fd7434193a8802222e51a32630ae6aaf020900000001ba6d17be00 | ||
1 output(s) for total of 35.087064732725 HMNY
| stealth address | amount | amount idx | tag |
| 00: ec7333f756f4c1d31d1d0a8a7dc05695ab83406451aa94624150633f9400d5ae | 35.087064732725 | 1607 of 0 | <98> |
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": 1513,
"vin": [ {
"gen": {
"height": 1453
}
}
],
"vout": [ {
"amount": 35087064732725,
"target": {
"tagged_key": {
"key": "ec7333f756f4c1d31d1d0a8a7dc05695ab83406451aa94624150633f9400d5ae",
"view_tag": "98"
}
}
}
],
"extra": [ 1, 28, 114, 114, 41, 146, 201, 109, 113, 26, 243, 194, 245, 199, 0, 50, 97, 253, 116, 52, 25, 58, 136, 2, 34, 46, 81, 163, 38, 48, 174, 106, 175, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}