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: 54804667289d917af86b44a9ff671a97b6c1ffd83b5aba383f473aecddf5d8d0
Tx prefix hash: c53c22566f43bedbdd1410cc777678459bbc990e40323ddd849837bece29d9d8
Tx public key: 0caf9fb77928d18caac1d3a15f1e80a95b30cb36dcb49623bb7baa9e15cbf90e
| Timestamp: 1780701487 | Timestamp [UTC]: 2026-06-05 23:18:07 | Age [y:d:h:m:s]: 00:003:02:17:50 |
| Block: 6059 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1827 | RingCT/type: yes/0 |
| Extra: 010caf9fb77928d18caac1d3a15f1e80a95b30cb36dcb49623bb7baa9e15cbf90e020900000002e49593ff00 | ||
1 output(s) for total of 34.780165946524 HMNY
| stealth address | amount | amount idx | tag |
| 00: 58aec363c9d9069eb409352ed6fcbc35159d040d8180c4bcdaace3ae73ca9fff | 34.780165946524 | 7528 of 0 | <e4> |
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": 6119,
"vin": [ {
"gen": {
"height": 6059
}
}
],
"vout": [ {
"amount": 34780165946524,
"target": {
"tagged_key": {
"key": "58aec363c9d9069eb409352ed6fcbc35159d040d8180c4bcdaace3ae73ca9fff",
"view_tag": "e4"
}
}
}
],
"extra": [ 1, 12, 175, 159, 183, 121, 40, 209, 140, 170, 193, 211, 161, 95, 30, 128, 169, 91, 48, 203, 54, 220, 180, 150, 35, 187, 123, 170, 158, 21, 203, 249, 14, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}