← previous blocknext block →recent activity
Analyzing
Block #94,471,727
17 transactions · 16 stateful · 2026-08-09 11:00:21 UTC
Parallelism
71/100
Blocked
31%
Avg conflicts / tx
0.82
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #94,471,727 · 17 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w08w19w210w314w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66bdb4c2…7ea6
0x34b655…2a6f
10 touches
10 conflicts
0xc44810d5…a00a
0x34b655…2a6f
8 touches
6 conflicts
0x74f95963…01a2
0x34b655…2a6f
6 touches
3 conflicts
0x78a1878b…7c15
0x34b655…2a6f
6 touches
3 conflicts
0x3cf50d44…961b
0x34b655…2a6f
6 touches
3 conflicts
0x7d7ed9e4…4a59
0x34b655…2a6f
6 touches
3 conflicts
0x1d0a04dd…b892
0x34b655…2a6f
6 touches
3 conflicts
0x7d7ed9e4…4a5a
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
10 conflicts on slot 0x66bdb4c268…a97ea6
Audit this contract →
← previous block·next block →recent activity