← previous blocknext block →recent activity
Analyzing
Block #94,065,266
11 transactions · 9 stateful · 2026-08-08 00:40:07 UTC
Parallelism
64/100
Blocked
33%
Avg conflicts / tx
0.36
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #94,065,266 · 11 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
3w07w18w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc3123313…7580
0x34b655…2a6f
6 touches
3 conflicts
0xdf6c3e51…c493
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x2a34bb88…04d5
0x34b655…2a6f
4 touches
1 conflict
0x2a34bb88…04d6
0x34b655…2a6f
4 touches
1 conflict
0x3cf50d44…961b
0x34b655…2a6f
4 touches
1 conflict
0x42e917f7…ed8c
0x34b655…2a6f
4 touches
1 conflict
0x84ba720a…1448
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 0xc3123313a5…af7580
Audit this contract →
← previous block·next block →recent activity