← previous blocknext block →recent activity
Analyzing
Block #94,794,440
20 transactions · 19 stateful · 2026-08-10 14:05:01 UTC
Parallelism
60/100
Blocked
47%
Avg conflicts / tx
1.1
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #94,794,440 · 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
2w03w14w25w26w37w48w412w014w515w618w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x03aa8b26…118a
0x34b655…2a6f
8 touches
6 conflicts
0x2840c278…bbc7
0x34b655…2a6f
8 touches
6 conflicts
0xf85fbefc…6825
0x34b655…2a6f
6 touches
3 conflicts
0x714da06b…bfa0
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0x9ba6ae4a…90cb
0x34b655…2a6f
6 touches
3 conflicts
0xabd0bcfc…64e2
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
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 0x03aa8b260f…60118a
Audit this contract →
← previous block·next block →recent activity