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: ebc0203e3826e1b638250baae65bb65d99ce482029fa1fd6049c6b2818024a6f
Tx prefix hash: 5fe1130acb6de14f7cbebe5a29bb73ae9fc7949f9ee6852bdc9afb6f030c2005
Tx public key: 0dd3a5b9748efc1fbea6fbfd9f922a9fc877146fe6e6577407c2f6da857481e0
| Timestamp: 1780717505 | Timestamp [UTC]: 2026-06-06 03:45:05 | Age [y:d:h:m:s]: 00:002:21:50:52 |
| Block: 6210 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1676 | RingCT/type: yes/0 |
| Extra: 010dd3a5b9748efc1fbea6fbfd9f922a9fc877146fe6e6577407c2f6da857481e0020900000002e49593ff00 | ||
1 output(s) for total of 34.770150356138 HMNY
| stealth address | amount | amount idx | tag |
| 00: ae8daf3ca2280e0fe568f44e425edef7c55757189220d369494ae0cecbe5a257 | 34.770150356138 | 7689 of 0 | <da> |
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": 6270,
"vin": [ {
"gen": {
"height": 6210
}
}
],
"vout": [ {
"amount": 34770150356138,
"target": {
"tagged_key": {
"key": "ae8daf3ca2280e0fe568f44e425edef7c55757189220d369494ae0cecbe5a257",
"view_tag": "da"
}
}
}
],
"extra": [ 1, 13, 211, 165, 185, 116, 142, 252, 31, 190, 166, 251, 253, 159, 146, 42, 159, 200, 119, 20, 111, 230, 230, 87, 116, 7, 194, 246, 218, 133, 116, 129, 224, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}