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: fd628cbc5ff03fc84e83fdd9e3f241a6471938954cbed9e22cb97299d3889e58
Tx prefix hash: b3e55049d9b4aae694559af4263b87ed18ac1e1d37f5adaf986ac38c6958abcb
Tx public key: 18e1587fd2153121db68c736c904a026e7e8054d7ecb64028514ad257aa01688
| Timestamp: 1780691988 | Timestamp [UTC]: 2026-06-05 20:39:48 | Age [y:d:h:m:s]: 00:003:04:06:59 |
| Block: 5766 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2120 | RingCT/type: yes/0 |
| Extra: 0118e1587fd2153121db68c736c904a026e7e8054d7ecb64028514ad257aa01688020900000001e49593ff00 | ||
1 output(s) for total of 34.799608402575 HMNY
| stealth address | amount | amount idx | tag |
| 00: 983c17897c8b2bd67c451e5728ac745d42dc523f62e709a551aa82626d31f282 | 34.799608402575 | 7221 of 0 | <2a> |
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": 5826,
"vin": [ {
"gen": {
"height": 5766
}
}
],
"vout": [ {
"amount": 34799608402575,
"target": {
"tagged_key": {
"key": "983c17897c8b2bd67c451e5728ac745d42dc523f62e709a551aa82626d31f282",
"view_tag": "2a"
}
}
}
],
"extra": [ 1, 24, 225, 88, 127, 210, 21, 49, 33, 219, 104, 199, 54, 201, 4, 160, 38, 231, 232, 5, 77, 126, 203, 100, 2, 133, 20, 173, 37, 122, 160, 22, 136, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}