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: 069cb6d7b4104fcae42ef12588896d1eabbf4fcf6ae141d803aaaea709b86e6e
Tx prefix hash: 2896c37de8ad4a42d028bd39edcfb271d046ef2b2332b5b4c359ecde529c2a2b
Tx public key: dab4d9d0f1c78ca841549e7b868b2baff0a9a313dd1186ca5ebedc3d5806a4d3
| Timestamp: 1780716004 | Timestamp [UTC]: 2026-06-06 03:20:04 | Age [y:d:h:m:s]: 00:007:07:42:12 |
| Block: 6199 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2546 | RingCT/type: yes/0 |
| Extra: 01dab4d9d0f1c78ca841549e7b868b2baff0a9a313dd1186ca5ebedc3d5806a4d3020900000006e49593ff00 | ||
1 output(s) for total of 34.770879871273 HMNY
| stealth address | amount | amount idx | tag |
| 00: fc59175d7ad61a5aa30d557f3afd56959ac50485558e1b90537dbffc648a045e | 34.770879871273 | 7678 of 0 | <dc> |
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": 6259,
"vin": [ {
"gen": {
"height": 6199
}
}
],
"vout": [ {
"amount": 34770879871273,
"target": {
"tagged_key": {
"key": "fc59175d7ad61a5aa30d557f3afd56959ac50485558e1b90537dbffc648a045e",
"view_tag": "dc"
}
}
}
],
"extra": [ 1, 218, 180, 217, 208, 241, 199, 140, 168, 65, 84, 158, 123, 134, 139, 43, 175, 240, 169, 163, 19, 221, 17, 134, 202, 94, 190, 220, 61, 88, 6, 164, 211, 2, 9, 0, 0, 0, 6, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}