← previous blocknext block →recent activity
Analyzing
Block #96,608,001
12 transactions · 10 stateful · 2026-08-16 22:23:07 UTC
Parallelism
83/100
Blocked
20%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,608,001 · 12 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xeafde96f…bf5e
0x34b655…2a6f
4 touches
1 conflict
0x574628e9…dcc3
0x34b655…2a6f
4 touches
1 conflict
0x6d1b72ee…6b78
0x34b655…2a6f
4 touches
1 conflict
0x1a69c7c5…09cc
0x34b655…2a6f
2 touches
0 conflicts
0x5d2e788d…5867
0x34b655…2a6f
2 touches
0 conflicts
0x711ceb8d…5202
0x34b655…2a6f
2 touches
0 conflicts
0x8a5ced1c…3b29
0x34b655…2a6f
2 touches
0 conflicts
0x9851de96…f25e
0x34b655…2a6f
2 touches
0 conflicts
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
1 conflict on slot 0xeafde96fa9…9cbf5e
Audit this contract →
← previous block·next block →recent activity