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: ced6877b3a453026ecc1d04f13d6195958ffa178e8d2b310b89a7422f96b4117
Tx prefix hash: 6dbf02bc766dfd6c2e0a2e268a6eba589ba40612d3cde605d08d8f390c3d180b
Tx public key: a0e8fe7fb6f32d4055106a882bbaab7c6f89fb0906ff9632f815d2672ae9b41d
| Timestamp: 1780691770 | Timestamp [UTC]: 2026-06-05 20:36:10 | Age [y:d:h:m:s]: 00:003:04:59:47 |
| Block: 5749 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2137 | RingCT/type: yes/0 |
| Extra: 01a0e8fe7fb6f32d4055106a882bbaab7c6f89fb0906ff9632f815d2672ae9b41d020900000001e49593ff00 | ||
1 output(s) for total of 34.800736796699 HMNY
| stealth address | amount | amount idx | tag |
| 00: d0e7bda8f7658713eb92fac81a2571669f56a8517a24e13d96cc71ffcef7622d | 34.800736796699 | 7202 of 0 | <7c> |
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": 5809,
"vin": [ {
"gen": {
"height": 5749
}
}
],
"vout": [ {
"amount": 34800736796699,
"target": {
"tagged_key": {
"key": "d0e7bda8f7658713eb92fac81a2571669f56a8517a24e13d96cc71ffcef7622d",
"view_tag": "7c"
}
}
}
],
"extra": [ 1, 160, 232, 254, 127, 182, 243, 45, 64, 85, 16, 106, 136, 43, 186, 171, 124, 111, 137, 251, 9, 6, 255, 150, 50, 248, 21, 210, 103, 42, 233, 180, 29, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}