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: c1a91ce767ab07e5253eb8575a42663b7763b57ef84fb9273261d670a55b7d87
Tx prefix hash: 956655f85a5623956163a1e2330b12900f7ea8e496a4d086e3f1d3bbbc47b26e
Tx public key: 3cc66b00b22ddd7a6c31ac912f0f3e957d23a4b5120c455abfc37eda60963c84
| Timestamp: 1780984430 | Timestamp [UTC]: 2026-06-09 05:53:50 | Age [y:d:h:m:s]: 00:000:10:05:54 |
| Block: 8114 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 577 | RingCT/type: yes/0 |
| Extra: 013cc66b00b22ddd7a6c31ac912f0f3e957d23a4b5120c455abfc37eda60963c84020900000002e49593ff00 | ||
1 output(s) for total of 34.644108248393 HMNY
| stealth address | amount | amount idx | tag |
| 00: e84fc25b5f962cfc252901079932f2d9514867eff660994d05fb3229847cdb3b | 34.644108248393 | 10050 of 0 | <db> |
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": 8174,
"vin": [ {
"gen": {
"height": 8114
}
}
],
"vout": [ {
"amount": 34644108248393,
"target": {
"tagged_key": {
"key": "e84fc25b5f962cfc252901079932f2d9514867eff660994d05fb3229847cdb3b",
"view_tag": "db"
}
}
}
],
"extra": [ 1, 60, 198, 107, 0, 178, 45, 221, 122, 108, 49, 172, 145, 47, 15, 62, 149, 125, 35, 164, 181, 18, 12, 69, 90, 191, 195, 126, 218, 96, 150, 60, 132, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}