← previous blocknext block →recent activity
Analyzing
Block #94,952,156
23 transactions · 22 stateful · 2026-08-11 03:18:21 UTC
Parallelism
78/100
Blocked
50%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #94,952,156 · 23 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
1w02w13w25w16w37w09w214w115w017w318w419w220w322w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x537258fd…eded
0x34b655…2a6f
8 touches
6 conflicts
0xa1087a5c…66c4
0x754704…b603
8 touches
6 conflicts
0x17350f18…0e1c
0xd32edf…ff58
7 touches
6 conflicts
0xeb148403…8601
0x065c9d…c394
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x3439dfbc…0d03
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xf5379ea4…bc3f
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
6 conflicts on slot 0x537258fd07…4eeded
Audit this contract →
← previous block·next block →recent activity