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: 5a6d20b672fce43e3a554565158dbeb3377058f295797b53ed98fe683399ce65
Tx prefix hash: b89705b3389b874416b1045dc4301061c12adc1175adc288a2bdec16b137d007
Tx public key: 18ec2c9e9e95ee216d1f75f6e84c70b7c4cb586dd65bb4d21b16dc2e8ced0fcc
| Timestamp: 1780686901 | Timestamp [UTC]: 2026-06-05 19:15:01 | Age [y:d:h:m:s]: 00:003:05:31:46 |
| Block: 5452 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2434 | RingCT/type: yes/0 |
| Extra: 0118ec2c9e9e95ee216d1f75f6e84c70b7c4cb586dd65bb4d21b16dc2e8ced0fcc020900000001e49593ff00 | ||
1 output(s) for total of 34.820456410298 HMNY
| stealth address | amount | amount idx | tag |
| 00: a1a3482a89fd65c7587135b110c41158c620348492eeac1cb9924e82cc9cf526 | 34.820456410298 | 6891 of 0 | <da> |
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": 5512,
"vin": [ {
"gen": {
"height": 5452
}
}
],
"vout": [ {
"amount": 34820456410298,
"target": {
"tagged_key": {
"key": "a1a3482a89fd65c7587135b110c41158c620348492eeac1cb9924e82cc9cf526",
"view_tag": "da"
}
}
}
],
"extra": [ 1, 24, 236, 44, 158, 158, 149, 238, 33, 109, 31, 117, 246, 232, 76, 112, 183, 196, 203, 88, 109, 214, 91, 180, 210, 27, 22, 220, 46, 140, 237, 15, 204, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}