← previous blocknext block →recent activity
Analyzing
Block #95,595,942
21 transactions · 21 stateful · 2026-08-13 09:30:54 UTC
Parallelism
71/100
Blocked
57%
Avg conflicts / tx
1.29
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #95,595,942 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w25w36w07w18w29w112w114w315w416w219w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc3207c1…fad6
0x34b655…2a6f
8 touches
6 conflicts
0x737acb78…fce8
0x34b655…2a6f
8 touches
6 conflicts
0xde93e7e6…f347
0x34b655…2a6f
8 touches
6 conflicts
0x0672e4a2…8d1f
0x34b655…2a6f
8 touches
6 conflicts
0xbde524f4…43bf
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0x08636046…e60f
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0xcc3207c136…affad6
Audit this contract →
← previous block·next block →recent activity