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: ef0e507c6ab03d29d63712620a508f1f1017be5955ae0001f33b8e975041c057
Tx prefix hash: ef13b78f63576c72e8ceac593b17c8e34c9cf14ce1fd15dafbd97138239e7a89
Tx public key: 7ecddba51b9142d69fe9061a09ac8f62a2e95ecdb5a684eae98ebcc32c374cb4
| Timestamp: 1780691830 | Timestamp [UTC]: 2026-06-05 20:37:10 | Age [y:d:h:m:s]: 00:003:02:41:43 |
| Block: 5757 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2129 | RingCT/type: yes/0 |
| Extra: 017ecddba51b9142d69fe9061a09ac8f62a2e95ecdb5a684eae98ebcc32c374cb4020900000001e49593ff00 | ||
1 output(s) for total of 34.800205783142 HMNY
| stealth address | amount | amount idx | tag |
| 00: 8428435b7245d5cde4fb394e588fb5f228c29b03c29c3d0dcef6c967565e5692 | 34.800205783142 | 7210 of 0 | <cb> |
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": 5817,
"vin": [ {
"gen": {
"height": 5757
}
}
],
"vout": [ {
"amount": 34800205783142,
"target": {
"tagged_key": {
"key": "8428435b7245d5cde4fb394e588fb5f228c29b03c29c3d0dcef6c967565e5692",
"view_tag": "cb"
}
}
}
],
"extra": [ 1, 126, 205, 219, 165, 27, 145, 66, 214, 159, 233, 6, 26, 9, 172, 143, 98, 162, 233, 94, 205, 181, 166, 132, 234, 233, 142, 188, 195, 44, 55, 76, 180, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}