← previous blocknext block →recent activity
Analyzing
Block #85,141,602
18 transactions · 16 stateful · 2026-07-02 15:45:37 UTC
Parallelism
72/100
Blocked
44%
Avg conflicts / tx
0.78
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,141,602 · 18 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
2w04w15w26w37w414w115w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf3cc02b3…f250
0x34b655…2a6f
10 touches
10 conflicts
0xf3fbc9b8…ab58
0x34b655…2a6f
10 touches
10 conflicts
0x922c7ebd…6600
0xc8689a…ee79
8 touches
6 conflicts
0x7ae63663…9d94
0x34b655…2a6f
8 touches
6 conflicts
0x8268029a…399a
0x34b655…2a6f
8 touches
6 conflicts
0x97c67486…27fe
0x34b655…2a6f
8 touches
6 conflicts
0xc83310b1…c778
0x34b655…2a6f
8 touches
6 conflicts
0xced67f0c…5126
0x34b655…2a6f
8 touches
6 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
10 conflicts on slot 0xf3cc02b355…4df250
Audit this contract →
← previous block·next block →recent activity