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: 0093b6fd1e73ae614d9b1bb3a7b12ecdddf6e32e75d3deadd52b7ee7fd30bf79
Tx prefix hash: 45ed9a9ae5a747e984673b9bc3a8a952b656da7927bd3b449965751099b23582
Tx public key: f12a4faa9e4ba2dce6642224e1a2a51eb0f79bd1e0b11bea55aecd084b6a4fb1
| Timestamp: 1780810602 | Timestamp [UTC]: 2026-06-07 05:36:42 | Age [y:d:h:m:s]: 00:001:19:59:15 |
| Block: 7019 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 867 | RingCT/type: yes/0 |
| Extra: 01f12a4faa9e4ba2dce6642224e1a2a51eb0f79bd1e0b11bea55aecd084b6a4fb1020900000001e49593ff00 | ||
1 output(s) for total of 34.716539769239 HMNY
| stealth address | amount | amount idx | tag |
| 00: b3c9bb22ecc34947d1a91732192ef4345ad821065dcb563e8a106cb008c12609 | 34.716539769239 | 8655 of 0 | <bb> |
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": 7079,
"vin": [ {
"gen": {
"height": 7019
}
}
],
"vout": [ {
"amount": 34716539769239,
"target": {
"tagged_key": {
"key": "b3c9bb22ecc34947d1a91732192ef4345ad821065dcb563e8a106cb008c12609",
"view_tag": "bb"
}
}
}
],
"extra": [ 1, 241, 42, 79, 170, 158, 75, 162, 220, 230, 100, 34, 36, 225, 162, 165, 30, 176, 247, 155, 209, 224, 177, 27, 234, 85, 174, 205, 8, 75, 106, 79, 177, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}