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: a13358cb4b8ab0fb5f45494cabfead4aceae40046e5f45f9d5c427c3d9e1e174
Tx prefix hash: c911dfbeba159e743cef854af71a2e2083a3c51d6b09fa4e41e99592c4f8148d
Tx public key: 6d631c1fdc53c5a9487c88229c35cbfa5b40692e87ed548feb650c52f4e8a078
| Timestamp: 1780797806 | Timestamp [UTC]: 2026-06-07 02:03:26 | Age [y:d:h:m:s]: 00:001:23:32:31 |
| Block: 6785 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1101 | RingCT/type: yes/0 |
| Extra: 016d631c1fdc53c5a9487c88229c35cbfa5b40692e87ed548feb650c52f4e8a078020900000001e49593ff00 | ||
1 output(s) for total of 34.732037913777 HMNY
| stealth address | amount | amount idx | tag |
| 00: bd3d4848e850f807581e402204593bc1bd48b3b8bec5a55bd3b095885b1632a2 | 34.732037913777 | 8379 of 0 | <63> |
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": 6845,
"vin": [ {
"gen": {
"height": 6785
}
}
],
"vout": [ {
"amount": 34732037913777,
"target": {
"tagged_key": {
"key": "bd3d4848e850f807581e402204593bc1bd48b3b8bec5a55bd3b095885b1632a2",
"view_tag": "63"
}
}
}
],
"extra": [ 1, 109, 99, 28, 31, 220, 83, 197, 169, 72, 124, 136, 34, 156, 53, 203, 250, 91, 64, 105, 46, 135, 237, 84, 143, 235, 101, 12, 82, 244, 232, 160, 120, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}