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: f332236c1429b87ae401231d18703dd71466f560bc82d49802610f7ab0283d33
Tx prefix hash: 45b03d5b1ebd79d9d65a91016224c14ca729d122b1d869d841812e997cd18941
Tx public key: 09aae2f56be3f40d3e2de6ef6314ed14ab29954ec929d539e81e31bbccd98440
| Timestamp: 1780707708 | Timestamp [UTC]: 2026-06-06 01:01:48 | Age [y:d:h:m:s]: 00:003:00:34:09 |
| Block: 6131 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1755 | RingCT/type: yes/0 |
| Extra: 0109aae2f56be3f40d3e2de6ef6314ed14ab29954ec929d539e81e31bbccd98440020900000001e49593ff00 | ||
1 output(s) for total of 34.775389940978 HMNY
| stealth address | amount | amount idx | tag |
| 00: e226a9068d10d0e8ebed3c2b6a9c8bb6448f09046b5cfd898d1a8d1ca6164d91 | 34.775389940978 | 7606 of 0 | <0c> |
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": 6191,
"vin": [ {
"gen": {
"height": 6131
}
}
],
"vout": [ {
"amount": 34775389940978,
"target": {
"tagged_key": {
"key": "e226a9068d10d0e8ebed3c2b6a9c8bb6448f09046b5cfd898d1a8d1ca6164d91",
"view_tag": "0c"
}
}
}
],
"extra": [ 1, 9, 170, 226, 245, 107, 227, 244, 13, 62, 45, 230, 239, 99, 20, 237, 20, 171, 41, 149, 78, 201, 41, 213, 57, 232, 30, 49, 187, 204, 217, 132, 64, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}