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: 51fc521618d2b27307b4ed36c17401e0bce1e174a85a86400ac5d9d4bf055434
Tx prefix hash: cdff35daf1f1981ea8236a7bf2df1b59756cf731da435e6794df82abb480832e
Tx public key: d8e4eff24522c2c107b2b27cc3b63d165532ddcc4a8a5a6dc0353a46ba907c08
| Timestamp: 1779784661 | Timestamp [UTC]: 2026-05-26 08:37:41 | Age [y:d:h:m:s]: 00:013:19:13:17 |
| Block: 2150 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5804 | RingCT/type: yes/0 |
| Extra: 01d8e4eff24522c2c107b2b27cc3b63d165532ddcc4a8a5a6dc0353a46ba907c0802090000000426697be300 | ||
1 output(s) for total of 35.040450164683 HMNY
| stealth address | amount | amount idx | tag |
| 00: 430e918937897f7b9cc55cbf05464c881914dada5c3f57292813b524b54ffbb8 | 35.040450164683 | 2480 of 0 | <dc> |
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": 2210,
"vin": [ {
"gen": {
"height": 2150
}
}
],
"vout": [ {
"amount": 35040450164683,
"target": {
"tagged_key": {
"key": "430e918937897f7b9cc55cbf05464c881914dada5c3f57292813b524b54ffbb8",
"view_tag": "dc"
}
}
}
],
"extra": [ 1, 216, 228, 239, 242, 69, 34, 194, 193, 7, 178, 178, 124, 195, 182, 61, 22, 85, 50, 221, 204, 74, 138, 90, 109, 192, 53, 58, 70, 186, 144, 124, 8, 2, 9, 0, 0, 0, 4, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}