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: 622ac42280c1cfdf1ceb3bea1a73d2080d3932f500d69c195c0e24670272993e
Tx prefix hash: 88c472f84d12bee14649249333d47acd1014a30d28194b87f1f80ac854d6cc29
Tx public key: 9116d12fa555efe604fd5bcfcff301e63afef031f9d551f65a6b1fbabe410e7f
| Timestamp: 1779721388 | Timestamp [UTC]: 2026-05-25 15:03:08 | Age [y:d:h:m:s]: 00:014:10:32:49 |
| Block: 1761 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6125 | RingCT/type: yes/0 |
| Extra: 019116d12fa555efe604fd5bcfcff301e63afef031f9d551f65a6b1fbabe410e7f020900000003ba6d17be00 | ||
1 output(s) for total of 35.066458400795 HMNY
| stealth address | amount | amount idx | tag |
| 00: 3e3fdc502e144e7e8d0a3621af7a4ba50225dc750e5dfd81aaa48d10c15cd348 | 35.066458400795 | 1944 of 0 | <60> |
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": 1821,
"vin": [ {
"gen": {
"height": 1761
}
}
],
"vout": [ {
"amount": 35066458400795,
"target": {
"tagged_key": {
"key": "3e3fdc502e144e7e8d0a3621af7a4ba50225dc750e5dfd81aaa48d10c15cd348",
"view_tag": "60"
}
}
}
],
"extra": [ 1, 145, 22, 209, 47, 165, 85, 239, 230, 4, 253, 91, 207, 207, 243, 1, 230, 58, 254, 240, 49, 249, 213, 81, 246, 90, 107, 31, 186, 190, 65, 14, 127, 2, 9, 0, 0, 0, 3, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}