← previous blocknext block →recent activity
Analyzing
Block #85,142,103
20 transactions · 20 stateful · 2026-07-02 15:48:58 UTC
Parallelism
70/100
Blocked
60%
Avg conflicts / tx
1.3
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #85,142,103 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w07w18w29w310w411w512w313w217w018w119w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
12 touches
15 conflicts
0x922c7ebd…6600
0xc8689a…ee79
8 touches
6 conflicts
0x7ae63663…9d94
0x34b655…2a6f
8 touches
6 conflicts
0x871e7b91…71a9
0x34b655…2a6f
8 touches
6 conflicts
0x97c67486…27fe
0x34b655…2a6f
8 touches
6 conflicts
0xc83310b1…c778
0x34b655…2a6f
8 touches
6 conflicts
0xc99e7125…81b1
0x34b655…2a6f
8 touches
6 conflicts
0xd66da5b7…7f25
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
15 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity