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: 4756ac3dfa2f1fd1325e7433caaf3236e7401d74157c03e25631c78490da4e75
Tx prefix hash: 8a0b5b86bda699e7d908327e2d10feb07bb39843b2d521685221beeec3ec811a
Tx public key: 83323ef81603755d28ee06ac935c3561c576570e7b5a7f590a37b3d6359ba953
| Timestamp: 1779786720 | Timestamp [UTC]: 2026-05-26 09:12:00 | Age [y:d:h:m:s]: 00:013:19:21:02 |
| Block: 2174 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5854 | RingCT/type: yes/0 |
| Extra: 0183323ef81603755d28ee06ac935c3561c576570e7b5a7f590a37b3d6359ba95302090000000126697be300 | ||
1 output(s) for total of 35.038846175353 HMNY
| stealth address | amount | amount idx | tag |
| 00: 655c8719493f3a54a3d2c5d2ee9be9e36c6fb01ebe6854128ddc13e178f421a7 | 35.038846175353 | 2512 of 0 | <59> |
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": 2234,
"vin": [ {
"gen": {
"height": 2174
}
}
],
"vout": [ {
"amount": 35038846175353,
"target": {
"tagged_key": {
"key": "655c8719493f3a54a3d2c5d2ee9be9e36c6fb01ebe6854128ddc13e178f421a7",
"view_tag": "59"
}
}
}
],
"extra": [ 1, 131, 50, 62, 248, 22, 3, 117, 93, 40, 238, 6, 172, 147, 92, 53, 97, 197, 118, 87, 14, 123, 90, 127, 89, 10, 55, 179, 214, 53, 155, 169, 83, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}