← previous blocknext block →recent activity
Analyzing
Block #94,680,528
25 transactions · 23 stateful · 2026-08-10 04:30:35 UTC
Parallelism
68/100
Blocked
48%
Avg conflicts / tx
0.84
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #94,680,528 · 25 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
1w03w04w16w011w112w213w214w315w416w517w619w121w723w024w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4f893478…c649
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xe2e52e46…0894
0x34b655…2a6f
6 touches
3 conflicts
0x4e135144…4167
0x34b655…2a6f
4 touches
1 conflict
0x810a3aa2…0227
0x34b655…2a6f
4 touches
1 conflict
0xa35509fa…5cb3
0x34b655…2a6f
4 touches
1 conflict
0xb37ed418…0a6c
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
10 conflicts on slot 0x4f89347868…acc649
Audit this contract →
← previous block·next block →recent activity