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: adbbd0996cfef864cf821d206b81eebde7f8310de2b82304399d96f2a6f9efdc
Tx prefix hash: 6696d87be49d530469979ecb6ab0bdabe91927b604ddbc49aafc44a2137d0d29
Tx public key: f13d4ef8a1cc725d3056b4c8632b322f97ae0519d07c23b2ad71bf251269339f
| Timestamp: 1780819727 | Timestamp [UTC]: 2026-06-07 08:08:47 | Age [y:d:h:m:s]: 00:001:15:10:06 |
| Block: 7144 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 742 | RingCT/type: yes/0 |
| Extra: 01f13d4ef8a1cc725d3056b4c8632b322f97ae0519d07c23b2ad71bf251269339f020900000001e49593ff00 | ||
1 output(s) for total of 34.708263679889 HMNY
| stealth address | amount | amount idx | tag |
| 00: ff578589872206e484c8d2ed85892873a7ad75c922924451c4d63ef5ec12e1c7 | 34.708263679889 | 8802 of 0 | <7b> |
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": 7204,
"vin": [ {
"gen": {
"height": 7144
}
}
],
"vout": [ {
"amount": 34708263679889,
"target": {
"tagged_key": {
"key": "ff578589872206e484c8d2ed85892873a7ad75c922924451c4d63ef5ec12e1c7",
"view_tag": "7b"
}
}
}
],
"extra": [ 1, 241, 61, 78, 248, 161, 204, 114, 93, 48, 86, 180, 200, 99, 43, 50, 47, 151, 174, 5, 25, 208, 124, 35, 178, 173, 113, 191, 37, 18, 105, 51, 159, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}