← previous blocknext block →recent activity
Analyzing
Block #85,130,423
18 transactions · 17 stateful · 2026-07-02 14:30:59 UTC
Parallelism
61/100
Blocked
59%
Avg conflicts / tx
1.72
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #85,130,423 · 18 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w37w08w19w210w113w314w415w516w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7fffd49d…772a
0x34b655…2a6f
10 touches
10 conflicts
0xf2112d98…bb04
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xdbea4a0f…a3aa
0x34b655…2a6f
8 touches
6 conflicts
0x7ee6007b…fd68
0x34b655…2a6f
6 touches
3 conflicts
0x8e5cc690…b06b
0x34b655…2a6f
6 touches
3 conflicts
0xc08384da…ecb7
0x34b655…2a6f
6 touches
3 conflicts
0xcb0cefcb…0d61
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
10 conflicts on slot 0x7fffd49db6…f8772a
Audit this contract →
← previous block·next block →recent activity