← previous blocknext block →recent activity
Analyzing
Block #94,739,962
20 transactions · 16 stateful · 2026-08-10 09:30:00 UTC
Parallelism
80/100
Blocked
31%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #94,739,962 · 20 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
2w03w15w06w112w213w014w315w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x267d92a4…197c
0x34b655…2a6f
6 touches
3 conflicts
0x4ac4de26…a5c8
0x34b655…2a6f
6 touches
3 conflicts
0x4f1ad4b4…e00a
0x34b655…2a6f
6 touches
3 conflicts
0x3439dfbc…0d03
0x34b655…2a6f
4 touches
1 conflict
0x37732607…ba00
0x34b655…2a6f
4 touches
1 conflict
0xb566cc65…214d
0xa6afd3…d132
4 touches
1 conflict
0x0ddfdaf2…9e00
0x34b655…2a6f
4 touches
1 conflict
0x2875d8d8…b7c3
0x34b655…2a6f
4 touches
1 conflict
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
3 conflicts on slot 0x267d92a46e…52197c
Audit this contract →
← previous block·next block →recent activity