← previous blocknext block →recent activity
Analyzing
Block #93,557,626
14 transactions · 14 stateful · 2026-08-06 06:07:16 UTC
Parallelism
71/100
Blocked
43%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,557,626 · 14 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w16w07w18w29w312w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xba352368…cbf1
0x34b655…2a6f
6 touches
3 conflicts
0xf55752a6…7afa
0x34b655…2a6f
6 touches
3 conflicts
0x1e56f6b6…5940
0x34b655…2a6f
6 touches
3 conflicts
0x28c50c6a…ebc8
0x34b655…2a6f
4 touches
1 conflict
0x291ccb8a…a0a0
0x34b655…2a6f
4 touches
1 conflict
0x4b92c351…ba92
0x34b655…2a6f
4 touches
1 conflict
0x6eb3e5af…064e
0x34b655…2a6f
4 touches
1 conflict
0x7a2fc410…c088
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
3 conflicts on slot 0xba352368db…b3cbf1
Audit this contract →
← previous block·next block →recent activity