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: 29307f489934a41d9bfa4e939d5c7d7df60c773a10fee5fd9ac4d94450f288da
Tx prefix hash: ca86e98e6935adf1fa766ed6b83cfa8398b3bf832b1b96f0bbcb073b7c9f3fb5
Tx public key: 930db174a02c9022405703d4f62f3c81c928376c773e21b20f4afebfa03a11e4
| Timestamp: 1780824279 | Timestamp [UTC]: 2026-06-07 09:24:39 | Age [y:d:h:m:s]: 00:009:22:57:40 |
| Block: 7231 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1514 | RingCT/type: yes/0 |
| Extra: 01930db174a02c9022405703d4f62f3c81c928376c773e21b20f4afebfa03a11e4020900000001e49593ff00 | ||
1 output(s) for total of 34.702504686175 HMNY
| stealth address | amount | amount idx | tag |
| 00: 1d1832ae9f89a18114dfc909335f6f9c030f84696facad3b3ef6c22299dbb02b | 34.702504686175 | 8905 of 0 | <98> |
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": 7291,
"vin": [ {
"gen": {
"height": 7231
}
}
],
"vout": [ {
"amount": 34702504686175,
"target": {
"tagged_key": {
"key": "1d1832ae9f89a18114dfc909335f6f9c030f84696facad3b3ef6c22299dbb02b",
"view_tag": "98"
}
}
}
],
"extra": [ 1, 147, 13, 177, 116, 160, 44, 144, 34, 64, 87, 3, 212, 246, 47, 60, 129, 201, 40, 55, 108, 119, 62, 33, 178, 15, 74, 254, 191, 160, 58, 17, 228, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}