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: 1d14896d7154341c491c6db9a711e9c1f91ca4cc829453c639d202c907b74986
Tx prefix hash: 1da046e5c27b9341e3b6638f3745dd03bbf13ada84ab79b340f17d6f899313a1
Tx public key: b4163aee393ae7b1a436e06265c32fe3bc5e98aa44d4210916bffff33e161558
| Timestamp: 1779435108 | Timestamp [UTC]: 2026-05-22 07:31:48 | Age [y:d:h:m:s]: 00:017:19:18:00 |
| Block: 116 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0918 kB |
| Tx version: 2 | No of confirmations: 7793 | RingCT/type: yes/0 |
| Extra: 01b4163aee393ae7b1a436e06265c32fe3bc5e98aa44d4210916bffff33e161558020900000001a662ed0300 | ||
1 output(s) for total of 35.176655408565 HMNY
| stealth address | amount | amount idx | tag |
| 00: e6f6cb38f17711b88a0b2ebee71b3c24d6765fd8923a93a0d2a532831e73bea6 | 35.176655408565 | 112 of 0 | <d2> |
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": 176,
"vin": [ {
"gen": {
"height": 116
}
}
],
"vout": [ {
"amount": 35176655408565,
"target": {
"tagged_key": {
"key": "e6f6cb38f17711b88a0b2ebee71b3c24d6765fd8923a93a0d2a532831e73bea6",
"view_tag": "d2"
}
}
}
],
"extra": [ 1, 180, 22, 58, 238, 57, 58, 231, 177, 164, 54, 224, 98, 101, 195, 47, 227, 188, 94, 152, 170, 68, 212, 33, 9, 22, 191, 255, 243, 62, 22, 21, 88, 2, 9, 0, 0, 0, 1, 166, 98, 237, 3, 0
],
"rct_signatures": {
"type": 0
}
}