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: 4f1c5ecf680a9888abbaacca073eb638fcc389533962312164c6241ac0c61df9
Tx prefix hash: d3293b9fa44e09eb5cb980444797d8a792c5690af386a77a7cfa744741e07adc
Tx public key: a5dc5de3f21f270975341eddc752df099068952fe8c688c87f4511002eaefecb
| Timestamp: 1780736598 | Timestamp [UTC]: 2026-06-06 09:03:18 | Age [y:d:h:m:s]: 00:002:14:15:35 |
| Block: 6368 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1518 | RingCT/type: yes/0 |
| Extra: 01a5dc5de3f21f270975341eddc752df099068952fe8c688c87f4511002eaefecb020900000002e49593ff00 | ||
1 output(s) for total of 34.759673554675 HMNY
| stealth address | amount | amount idx | tag |
| 00: 2b3fb4fdcd1ab0c3929e210f4e7597dc5d65f95aeefa254274eb1a5b002ead40 | 34.759673554675 | 7857 of 0 | <7b> |
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": 6428,
"vin": [ {
"gen": {
"height": 6368
}
}
],
"vout": [ {
"amount": 34759673554675,
"target": {
"tagged_key": {
"key": "2b3fb4fdcd1ab0c3929e210f4e7597dc5d65f95aeefa254274eb1a5b002ead40",
"view_tag": "7b"
}
}
}
],
"extra": [ 1, 165, 220, 93, 227, 242, 31, 39, 9, 117, 52, 30, 221, 199, 82, 223, 9, 144, 104, 149, 47, 232, 198, 136, 200, 127, 69, 17, 0, 46, 174, 254, 203, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}