← previous blocknext block →recent activity
Analyzing
Block #85,135,947
43 transactions · 33 stateful · 2026-07-02 15:07:52 UTC
Parallelism
65/100
Blocked
67%
Avg conflicts / tx
1.88
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #85,135,947 · 43 txs across 15 waves · depth 15
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w06w17w210w316w017w118w219w320w421w522w623w724w828w331w432w533w1036w1137w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
20 touches
45 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xf4150f34…bfea
0x34b655…2a6f
8 touches
6 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
8 touches
6 conflicts
0x4c56e2d6…0a93
0x34b655…2a6f
8 touches
6 conflicts
0x0a6f5e37…6c3c
0x34b655…2a6f
8 touches
6 conflicts
0x6bdb9869…7558
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
45 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity