← previous blocknext block →recent activity
Analyzing
Block #96,265,942
11 transactions · 8 stateful · 2026-08-15 17:42:24 UTC
Parallelism
64/100
Blocked
38%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,265,942 · 11 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
4w05w16w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66bdb4c2…7ea6
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x7ff8446b…de92
0x34b655…2a6f
4 touches
1 conflict
0x243614ab…33fa
0x34b655…2a6f
4 touches
1 conflict
0xf4db760d…fc5b
0x34b655…2a6f
4 touches
1 conflict
0xf4db760d…fc5c
0x34b655…2a6f
4 touches
1 conflict
0xf6592f84…e937
0x34b655…2a6f
4 touches
1 conflict
0x3fd6704a…63a9
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 0x66bdb4c268…a97ea6
Audit this contract →
← previous block·next block →recent activity