← previous blocknext block →recent activity
Analyzing
Block #94,791,852
21 transactions · 18 stateful · 2026-08-10 13:52:00 UTC
Parallelism
81/100
Blocked
50%
Avg conflicts / tx
1.05
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #94,791,852 · 21 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w07w08w19w215w216w017w218w319w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x40c49f…2af0
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0x76d1e78d…7877
0x40c49f…2af0
8 touches
6 conflicts
0x5d46e6a0…5ed9
0x40c49f…2af0
8 touches
6 conflicts
0x2170188e…c17b
0x34b655…2a6f
6 touches
3 conflicts
0x46ee3c65…4ab8
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
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: 0x40c49f17…d22af0
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity