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: fa9bdbfd32c56f04db70c2c5a55a253f61cdf94c8febc602d65576ca2f989750
Tx prefix hash: 9251b484f7bf3064706b1846aade5ac62ce5dfbd6807e4fdb3c04f4f3e71e168
Tx public key: bef737fec9d74fe5dbbdfc9da61e3bca191011437d76337d375b986c3bfd0123
| Timestamp: 1779470821 | Timestamp [UTC]: 2026-05-22 17:27:01 | Age [y:d:h:m:s]: 00:025:14:55:18 |
| Block: 560 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 8185 | RingCT/type: yes/0 |
| Extra: 01bef737fec9d74fe5dbbdfc9da61e3bca191011437d76337d375b986c3bfd012302090000000293369e7d00 | ||
1 output(s) for total of 35.146878189909 HMNY
| stealth address | amount | amount idx | tag |
| 00: e3a9bd1cf0490319442e3c1e63e4480ec7f3878fdfcf726d8397189c4df7852b | 35.146878189909 | 568 of 0 | <dd> |
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": 620,
"vin": [ {
"gen": {
"height": 560
}
}
],
"vout": [ {
"amount": 35146878189909,
"target": {
"tagged_key": {
"key": "e3a9bd1cf0490319442e3c1e63e4480ec7f3878fdfcf726d8397189c4df7852b",
"view_tag": "dd"
}
}
}
],
"extra": [ 1, 190, 247, 55, 254, 201, 215, 79, 229, 219, 189, 252, 157, 166, 30, 59, 202, 25, 16, 17, 67, 125, 118, 51, 125, 55, 91, 152, 108, 59, 253, 1, 35, 2, 9, 0, 0, 0, 2, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}