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: a5ec0b0b12cff11cfc09a2a2e3b8fc61f148b43b85daf4067d50c28c9391f82d
Tx prefix hash: 728eeb0dbccef8ef64dcc50948d83129ad4ae623c62888186ae521eede5af69a
Tx public key: d7fbcf6ceef97aeed0a27bf63b28e6edf1758a23ef9ec4e0fb1b3277f6f5ab45
| Timestamp: 1780323131 | Timestamp [UTC]: 2026-06-01 14:12:11 | Age [y:d:h:m:s]: 00:007:13:26:39 |
| Block: 5059 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2890 | RingCT/type: yes/0 |
| Extra: 01d7fbcf6ceef97aeed0a27bf63b28e6edf1758a23ef9ec4e0fb1b3277f6f5ab4502090000004126697be300 | ||
1 output(s) for total of 34.846567216872 HMNY
| stealth address | amount | amount idx | tag |
| 00: 9f6ebc1e3ab5b2aef2f219da49d876b274ad3f1c6c2b4cd880f4820d2be06bdf | 34.846567216872 | 6434 of 0 | <69> |
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": 5119,
"vin": [ {
"gen": {
"height": 5059
}
}
],
"vout": [ {
"amount": 34846567216872,
"target": {
"tagged_key": {
"key": "9f6ebc1e3ab5b2aef2f219da49d876b274ad3f1c6c2b4cd880f4820d2be06bdf",
"view_tag": "69"
}
}
}
],
"extra": [ 1, 215, 251, 207, 108, 238, 249, 122, 238, 208, 162, 123, 246, 59, 40, 230, 237, 241, 117, 138, 35, 239, 158, 196, 224, 251, 27, 50, 119, 246, 245, 171, 69, 2, 9, 0, 0, 0, 65, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}