← previous blocknext block →recent activity
Analyzing
Block #94,806,601
18 transactions · 18 stateful · 2026-08-10 15:06:12 UTC
Parallelism
78/100
Blocked
44%
Avg conflicts / tx
0.83
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #94,806,601 · 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
1w02w13w24w37w310w011w114w015w116w217w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x711b76ab…932a
0xd32edf…ff58
7 touches
6 conflicts
0x13e95b46…6cb1
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x00a19519…11c6
0x34b655…2a6f
6 touches
3 conflicts
0x3a2b650f…f454
0x34b655…2a6f
6 touches
3 conflicts
0x81d2ebf9…2915
0x34b655…2a6f
6 touches
3 conflicts
0x98862f54…62ca
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity