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: e032baec86f9c5ac270ab7b8156103a5b7f5d121186fd40ff654c6352c9afcab
Tx prefix hash: 4d4362f72d8af83502362deec39b63fdeb4aacf3e7f46c3df7c9066c94517138
Tx public key: abd5c550483ac275f4b1cd298a1d78f75ce54d4fcc4da1f9b3ee0c34ed5606f8
| Timestamp: 1779851192 | Timestamp [UTC]: 2026-05-27 03:06:32 | Age [y:d:h:m:s]: 00:012:22:29:25 |
| Block: 2531 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5355 | RingCT/type: yes/0 |
| Extra: 01abd5c550483ac275f4b1cd298a1d78f75ce54d4fcc4da1f9b3ee0c34ed5606f802090000000226697be300 | ||
1 output(s) for total of 35.014995501331 HMNY
| stealth address | amount | amount idx | tag |
| 00: 9eea63ea17e9a5557b4771951054ced694d007e422de56a888d292cba29dc528 | 35.014995501331 | 2979 of 0 | <b4> |
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": 2591,
"vin": [ {
"gen": {
"height": 2531
}
}
],
"vout": [ {
"amount": 35014995501331,
"target": {
"tagged_key": {
"key": "9eea63ea17e9a5557b4771951054ced694d007e422de56a888d292cba29dc528",
"view_tag": "b4"
}
}
}
],
"extra": [ 1, 171, 213, 197, 80, 72, 58, 194, 117, 244, 177, 205, 41, 138, 29, 120, 247, 92, 229, 77, 79, 204, 77, 161, 249, 179, 238, 12, 52, 237, 86, 6, 248, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}