← previous blocknext block →recent activity
Analyzing
Block #94,846,313
20 transactions · 19 stateful · 2026-08-10 18:26:00 UTC
Parallelism
60/100
Blocked
58%
Avg conflicts / tx
2.4
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #94,846,313 · 20 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w25w37w48w49w510w611w514w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd30f9e74…d404
0x34b655…2a6f
16 touches
28 conflicts
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x289b2009…512c
0x34b655…2a6f
10 touches
10 conflicts
0x4d94334a…8a96
0x34b655…2a6f
8 touches
6 conflicts
0x524f0872…0d12
0x34b655…2a6f
8 touches
6 conflicts
0x2f475d04…03fa
0x34b655…2a6f
8 touches
6 conflicts
0x5e3014f0…b4e1
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
28 conflicts on slot 0xd30f9e74d6…9ed404
Audit this contract →
← previous block·next block →recent activity