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: 221e1eef8d28ac24944b3f1c598d2af96544c252784322b669e86caeff9c45fc
Tx prefix hash: ac4f01552726095e70382363946d0734e38634d2a05af0464fef17f77e1ed071
Tx public key: d889a6ad2cd7d43d8a4fd6e662aa899443eb8d53c926f3daa22218045b64e3ad
| Timestamp: 1780836496 | Timestamp [UTC]: 2026-06-07 12:48:16 | Age [y:d:h:m:s]: 00:001:15:44:46 |
| Block: 7416 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 636 | RingCT/type: yes/0 |
| Extra: 01d889a6ad2cd7d43d8a4fd6e662aa899443eb8d53c926f3daa22218045b64e3ad020900000002e49593ff00 | ||
1 output(s) for total of 34.690261726298 HMNY
| stealth address | amount | amount idx | tag |
| 00: d9964ed53ec7e015fd79e2d2d3cc8911b3369b409c74e67359eacc05c5005920 | 34.690261726298 | 9130 of 0 | <dd> |
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": 7476,
"vin": [ {
"gen": {
"height": 7416
}
}
],
"vout": [ {
"amount": 34690261726298,
"target": {
"tagged_key": {
"key": "d9964ed53ec7e015fd79e2d2d3cc8911b3369b409c74e67359eacc05c5005920",
"view_tag": "dd"
}
}
}
],
"extra": [ 1, 216, 137, 166, 173, 44, 215, 212, 61, 138, 79, 214, 230, 98, 170, 137, 148, 67, 235, 141, 83, 201, 38, 243, 218, 162, 34, 24, 4, 91, 100, 227, 173, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}