← previous blocknext block →recent activity
Analyzing
Block #94,968,942
18 transactions · 18 stateful · 2026-08-11 04:42:46 UTC
Parallelism
78/100
Blocked
28%
Avg conflicts / tx
0.33
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #94,968,942 · 18 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
2w03w04w15w211w313w114w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x30a41252…2f10
0x34b655…2a6f
4 touches
1 conflict
0xc2bbb61a…46fe
0x968279…9342
4 touches
1 conflict
0xc2bbb61a…46f8
0x968279…9342
4 touches
1 conflict
0xc2bbb61a…46fb
0x968279…9342
4 touches
1 conflict
0xc2bbb61a…46fc
0x968279…9342
4 touches
1 conflict
0xea02471d…1542
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 0xbde524f475…b143bf
Audit this contract →
← previous block·next block →recent activity