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: 983a622e33991349c96158f76082bb567eb964f786b2d2c2565ee621e2e7b6e4
Tx prefix hash: 18e6b213243354280e5bbe724df6288a7436e5f0e4bc3a732484d24b88d85087
Tx public key: 58d283fd1e97037ef3b81f04ef12ae3c2a24d0d0d88af51b18af26960c43789f
| Timestamp: 1779783660 | Timestamp [UTC]: 2026-05-26 08:21:00 | Age [y:d:h:m:s]: 00:013:18:19:36 |
| Block: 2137 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5760 | RingCT/type: yes/0 |
| Extra: 0158d283fd1e97037ef3b81f04ef12ae3c2a24d0d0d88af51b18af26960c43789f02090000000326697be300 | ||
1 output(s) for total of 35.041319022895 HMNY
| stealth address | amount | amount idx | tag |
| 00: 887265db190455ca7d4767235a059a00a19557ebcad93c9dd106f04f25cd1be0 | 35.041319022895 | 2465 of 0 | <61> |
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": 2197,
"vin": [ {
"gen": {
"height": 2137
}
}
],
"vout": [ {
"amount": 35041319022895,
"target": {
"tagged_key": {
"key": "887265db190455ca7d4767235a059a00a19557ebcad93c9dd106f04f25cd1be0",
"view_tag": "61"
}
}
}
],
"extra": [ 1, 88, 210, 131, 253, 30, 151, 3, 126, 243, 184, 31, 4, 239, 18, 174, 60, 42, 36, 208, 208, 216, 138, 245, 27, 24, 175, 38, 150, 12, 67, 120, 159, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}