← previous blocknext block →recent activity
Analyzing
Block #83,636,283
23 transactions · 19 stateful · 2026-06-25 16:28:20 UTC
Parallelism
78/100
Blocked
32%
Avg conflicts / tx
0.52
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,636,283 · 23 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w16w07w18w29w313w017w318w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc1526f9e…82d5
0x34b655…2a6f
8 touches
6 conflicts
0x7fe97198…79ab
0x34b655…2a6f
6 touches
3 conflicts
0x9ad4d28a…c788
0x34b655…2a6f
6 touches
3 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0xd064a456…b881
0x34b655…2a6f
6 touches
3 conflicts
0x5afc4280…bb91
0x34b655…2a6f
4 touches
1 conflict
0x5fad6fee…7714
0x34b655…2a6f
4 touches
1 conflict
0x7c93b38a…9e69
0x34b655…2a6f
4 touches
1 conflict
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Perpl
6 conflicts on slot 0xc1526f9e7b…c282d5
Audit this contract →
← previous block·next block →recent activity