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: 792140acb18d50535d664579c5fea28736921074720b9be201285cc9ff678dfc
Tx prefix hash: 361dc5a7450f84806e202888bb8c27a4d2e7fa94516e0ddde4602cce438b19c8
Tx public key: bb61453f1503d4576e3d630157c980a3e848b7ba7a3f59648321bced0bc1b46c
| Timestamp: 1780846838 | Timestamp [UTC]: 2026-06-07 15:40:38 | Age [y:d:h:m:s]: 00:001:09:06:09 |
| Block: 7515 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 371 | RingCT/type: yes/0 |
| Extra: 01bb61453f1503d4576e3d630157c980a3e848b7ba7a3f59648321bced0bc1b46c020900000003e49593ff00 | ||
1 output(s) for total of 34.683711862564 HMNY
| stealth address | amount | amount idx | tag |
| 00: 7ca7ef361ec1c6345db49b6fb02837a66a3af59de0d40dab417ac62f34d22902 | 34.683711862564 | 9265 of 0 | <9e> |
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": 7575,
"vin": [ {
"gen": {
"height": 7515
}
}
],
"vout": [ {
"amount": 34683711862564,
"target": {
"tagged_key": {
"key": "7ca7ef361ec1c6345db49b6fb02837a66a3af59de0d40dab417ac62f34d22902",
"view_tag": "9e"
}
}
}
],
"extra": [ 1, 187, 97, 69, 63, 21, 3, 212, 87, 110, 61, 99, 1, 87, 201, 128, 163, 232, 72, 183, 186, 122, 63, 89, 100, 131, 33, 188, 237, 11, 193, 180, 108, 2, 9, 0, 0, 0, 3, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}