← previous blocknext block →recent activity
Analyzing
Block #94,848,649
25 transactions · 21 stateful · 2026-08-10 18:37:45 UTC
Parallelism
68/100
Blocked
57%
Avg conflicts / tx
1.4
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #94,848,649 · 25 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
5w06w17w18w29w210w211w317w419w520w623w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xd66696e0…0842
0x34b655…2a6f
8 touches
6 conflicts
0x3b9bb58c…e73a
0x34b655…2a6f
8 touches
6 conflicts
0xfefb0189…f726
0x34b655…2a6f
8 touches
6 conflicts
0x7be3246e…f89f
0x34b655…2a6f
8 touches
6 conflicts
0x80a49a52…b8af
0x34b655…2a6f
7 touches
6 conflicts
0x00000000…00c9
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
21 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity