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: ef31e67872d4c49222730434c28773bba4c9a060351e4cfe0b675f32f18770ce
Tx prefix hash: c1643774453d10a66038ddca4ae34e1e9242cff33fd03170241670525f2e4cfb
Tx public key: 0e2d500cc927bb524c6696e3fd63dc125fee4c5a127556213b80984f675715a7
| Timestamp: 1780848578 | Timestamp [UTC]: 2026-06-07 16:09:38 | Age [y:d:h:m:s]: 00:001:07:09:15 |
| Block: 7527 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 359 | RingCT/type: yes/0 |
| Extra: 010e2d500cc927bb524c6696e3fd63dc125fee4c5a127556213b80984f675715a7020900000003e49593ff00 | ||
1 output(s) for total of 34.687940023727 HMNY
| stealth address | amount | amount idx | tag |
| 00: c29a1031f924faf72490899e1e805e7a14b627724fc3c0e217ca97d099c1369b | 34.687940023727 | 9281 of 0 | <14> |
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": 7587,
"vin": [ {
"gen": {
"height": 7527
}
}
],
"vout": [ {
"amount": 34687940023727,
"target": {
"tagged_key": {
"key": "c29a1031f924faf72490899e1e805e7a14b627724fc3c0e217ca97d099c1369b",
"view_tag": "14"
}
}
}
],
"extra": [ 1, 14, 45, 80, 12, 201, 39, 187, 82, 76, 102, 150, 227, 253, 99, 220, 18, 95, 238, 76, 90, 18, 117, 86, 33, 59, 128, 152, 79, 103, 87, 21, 167, 2, 9, 0, 0, 0, 3, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}