← previous blocknext block →recent activity
Analyzing
Block #85,160,807
17 transactions · 16 stateful · 2026-07-02 17:53:28 UTC
Parallelism
59/100
Blocked
63%
Avg conflicts / tx
2.41
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #85,160,807 · 17 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
4w05w16w27w38w49w512w113w314w415w516w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb44d5376…33cc
0x34b655…2a6f
14 touches
21 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
14 touches
21 conflicts
0xf324b405…ca30
0x34b655…2a6f
12 touches
15 conflicts
0x06aed19e…ca57
0x34b655…2a6f
10 touches
10 conflicts
0x548145a9…cfce
0x34b655…2a6f
10 touches
10 conflicts
0x63b15849…80b2
0x34b655…2a6f
10 touches
10 conflicts
0xa1571d54…ae41
0x34b655…2a6f
10 touches
10 conflicts
0xcfa965cc…6fcf
0x34b655…2a6f
10 touches
10 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
21 conflicts on slot 0xb44d5376ca…0b33cc
Audit this contract →
← previous block·next block →recent activity