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: 62effd6147a8ff1d9f50daff14e776bd14ed37ceeb411b6b1bc28e9402a16743
Tx prefix hash: 181180365f0b1ae75fd8f9d63ca1c47433b6b490e9fee4e68fbbb971e5d7f81c
Tx public key: a8d2613b434127d7d10d413765f6489498e34d43db45b19054484d50e20d3ccd
| Timestamp: 1780043783 | Timestamp [UTC]: 2026-05-29 08:36:23 | Age [y:d:h:m:s]: 00:010:14:42:30 |
| Block: 4318 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3568 | RingCT/type: yes/0 |
| Extra: 01a8d2613b434127d7d10d413765f6489498e34d43db45b19054484d50e20d3ccd02090000000126697be300 | ||
1 output(s) for total of 34.895852317387 HMNY
| stealth address | amount | amount idx | tag |
| 00: 595c86c7e8353081cbcb0329e5eb7ffe6e75c11700155e942f6b75f7ec3d7250 | 34.895852317387 | 5396 of 0 | <2f> |
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": 4378,
"vin": [ {
"gen": {
"height": 4318
}
}
],
"vout": [ {
"amount": 34895852317387,
"target": {
"tagged_key": {
"key": "595c86c7e8353081cbcb0329e5eb7ffe6e75c11700155e942f6b75f7ec3d7250",
"view_tag": "2f"
}
}
}
],
"extra": [ 1, 168, 210, 97, 59, 67, 65, 39, 215, 209, 13, 65, 55, 101, 246, 72, 148, 152, 227, 77, 67, 219, 69, 177, 144, 84, 72, 77, 80, 226, 13, 60, 205, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}