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: dbf98424050abf7ecf6afa6f89dedce6d85f20e167dbb129170fdb386f29630e
Tx prefix hash: 7ba0c16104fc265d07fb4a87eb359c2871d2cbc43e7876c23d779ebe8d6b0d61
Tx public key: 036b9185ab60979c2f0722e57ea63c51363787d2da574f46549f41238f7b5515
| Timestamp: 1780996830 | Timestamp [UTC]: 2026-06-09 09:20:30 | Age [y:d:h:m:s]: 00:000:05:28:25 |
| Block: 8362 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 278 | RingCT/type: yes/0 |
| Extra: 01036b9185ab60979c2f0722e57ea63c51363787d2da574f46549f41238f7b5515020900000002e49593ff00 | ||
1 output(s) for total of 34.627724666634 HMNY
| stealth address | amount | amount idx | tag |
| 00: 63dd15229973cb061e0c74941db1ae3e42ee3ef3a83368bcdc05defcc16b3321 | 34.627724666634 | 10340 of 0 | <3e> |
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": 8422,
"vin": [ {
"gen": {
"height": 8362
}
}
],
"vout": [ {
"amount": 34627724666634,
"target": {
"tagged_key": {
"key": "63dd15229973cb061e0c74941db1ae3e42ee3ef3a83368bcdc05defcc16b3321",
"view_tag": "3e"
}
}
}
],
"extra": [ 1, 3, 107, 145, 133, 171, 96, 151, 156, 47, 7, 34, 229, 126, 166, 60, 81, 54, 55, 135, 210, 218, 87, 79, 70, 84, 159, 65, 35, 143, 123, 85, 21, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}