← previous blocknext block →recent activity
Analyzing
Block #95,743,754
8 transactions · 7 stateful · 2026-08-13 21:55:25 UTC
Parallelism
63/100
Blocked
43%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #95,743,754 · 8 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2210fbde…49cc
0x34b655…2a6f
6 touches
3 conflicts
0x0778475b…bd75
0x2a68ba…90c5
4 touches
1 conflict
0x4b5c5869…b618
0x065c9d…c394
3 touches
1 conflict
0x48b13e5e…3c2a
0x34b655…2a6f
2 touches
0 conflicts
0x5df7cf2b…bbe5
0x34b655…2a6f
2 touches
0 conflicts
0x5f19a4ec…e276
0x34b655…2a6f
2 touches
0 conflicts
0x620b761c…270e
0x34b655…2a6f
2 touches
0 conflicts
0x75ab7c35…0913
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
3 conflicts on slot 0x2210fbde2a…3849cc
Audit this contract →
← previous block·next block →recent activity