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: 80c37ef7fa2ba70d63250b2d3893280e0026375cf1101a4f929e198371b346e7
Tx prefix hash: 969e519dc4023a76697f501b61d680ca7ae7c1e2ff33fa9413845020eebd4ac3
Tx public key: 16629eef0a4d3dabc8787418df1d73049673bb2cd5add02527d50f4fe6bb4d8e
| Timestamp: 1780797641 | Timestamp [UTC]: 2026-06-07 02:00:41 | Age [y:d:h:m:s]: 00:001:23:35:16 |
| Block: 6782 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1104 | RingCT/type: yes/0 |
| Extra: 0116629eef0a4d3dabc8787418df1d73049673bb2cd5add02527d50f4fe6bb4d8e020900000001e49593ff00 | ||
1 output(s) for total of 34.732236652850 HMNY
| stealth address | amount | amount idx | tag |
| 00: 51c73a45c7eda0e965f2ce0f4dee0644682f45cc9bc896451ebab02eafdf5982 | 34.732236652850 | 8376 of 0 | <ee> |
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": 6842,
"vin": [ {
"gen": {
"height": 6782
}
}
],
"vout": [ {
"amount": 34732236652850,
"target": {
"tagged_key": {
"key": "51c73a45c7eda0e965f2ce0f4dee0644682f45cc9bc896451ebab02eafdf5982",
"view_tag": "ee"
}
}
}
],
"extra": [ 1, 22, 98, 158, 239, 10, 77, 61, 171, 200, 120, 116, 24, 223, 29, 115, 4, 150, 115, 187, 44, 213, 173, 208, 37, 39, 213, 15, 79, 230, 187, 77, 142, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}