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: d8dee8654a397293bd43d5bf1f510977b6bcc5683824ab6772d05bf685c91e6e
Tx prefix hash: 0f18aa97e4f9ab8c04c54f8d6b9c71ac4147625810bc0b06c082267fa9ff9398
Tx public key: 42e766af0266f452aa536d92879def085e545bf7b839abcd9c4163eab45fd848
| Timestamp: 1780685670 | Timestamp [UTC]: 2026-06-05 18:54:30 | Age [y:d:h:m:s]: 00:003:07:46:06 |
| Block: 5397 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2500 | RingCT/type: yes/0 |
| Extra: 0142e766af0266f452aa536d92879def085e545bf7b839abcd9c4163eab45fd848020900000002e49593ff00 | ||
1 output(s) for total of 34.824109416632 HMNY
| stealth address | amount | amount idx | tag |
| 00: dc6e0e2d72574bba96c8fb0daf2e02acc5bb4701fc74fbb04ce1fe42663bf5cf | 34.824109416632 | 6834 of 0 | <da> |
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": 5457,
"vin": [ {
"gen": {
"height": 5397
}
}
],
"vout": [ {
"amount": 34824109416632,
"target": {
"tagged_key": {
"key": "dc6e0e2d72574bba96c8fb0daf2e02acc5bb4701fc74fbb04ce1fe42663bf5cf",
"view_tag": "da"
}
}
}
],
"extra": [ 1, 66, 231, 102, 175, 2, 102, 244, 82, 170, 83, 109, 146, 135, 157, 239, 8, 94, 84, 91, 247, 184, 57, 171, 205, 156, 65, 99, 234, 180, 95, 216, 72, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}