← previous blocknext block →recent activity
Analyzing
Block #95,154,844
20 transactions · 17 stateful · 2026-08-11 20:18:41 UTC
Parallelism
70/100
Blocked
59%
Avg conflicts / tx
1.3
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #95,154,844 · 20 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
1w02w13w04w15w26w07w18w211w112w315w316w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x86b6d4a1…728c
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xd66696e0…0842
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x91606dbf…a25d
0x34b655…2a6f
6 touches
3 conflicts
0x966e45cf…0f25
0x34b655…2a6f
6 touches
3 conflicts
0x9a9383a9…6bc7
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 0x86b6d4a127…d9728c
Audit this contract →
← previous block·next block →recent activity