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: 44153e9df9648d96a553f0df1ae6a990ffe3d598deca86e8e19f8c12f437b4b1
Tx prefix hash: b7d090f76319e45ce298b58e6c90d805bce85227cb0c2aeab2d43fe6500001a6
Tx public key: e09bd2e309333a2b63cdbfa282c4b33e081ee9f1a84c4d170734f095f7721edd
| Timestamp: 1781007783 | Timestamp [UTC]: 2026-06-09 12:23:03 | Age [y:d:h:m:s]: 00:000:03:24:34 |
| Block: 8569 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 112 | RingCT/type: yes/0 |
| Extra: 01e09bd2e309333a2b63cdbfa282c4b33e081ee9f1a84c4d170734f095f7721edd020900000002e49593ff00 | ||
1 output(s) for total of 34.614055593533 HMNY
| stealth address | amount | amount idx | tag |
| 00: 16f5ac4c7afabffaeb22df5273d223a89642b1fefa4cfd2798b809e2583a73c6 | 34.614055593533 | 10583 of 0 | <99> |
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": 8629,
"vin": [ {
"gen": {
"height": 8569
}
}
],
"vout": [ {
"amount": 34614055593533,
"target": {
"tagged_key": {
"key": "16f5ac4c7afabffaeb22df5273d223a89642b1fefa4cfd2798b809e2583a73c6",
"view_tag": "99"
}
}
}
],
"extra": [ 1, 224, 155, 210, 227, 9, 51, 58, 43, 99, 205, 191, 162, 130, 196, 179, 62, 8, 30, 233, 241, 168, 76, 77, 23, 7, 52, 240, 149, 247, 114, 30, 221, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}