← previous blocknext block →recent activity
Analyzing
Block #85,352,009
54 transactions · 48 stateful · 2026-07-03 15:07:01 UTC
Parallelism
65/100
Blocked
63%
Avg conflicts / tx
2.19
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #85,352,009 · 54 txs across 19 waves · depth 19
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
wave w15
wave w16
wave w17
wave w18
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w211w012w114w316w017w118w219w320w034w735w836w238w340w441w945w1046w1153w18
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
18 touches
36 conflicts
0xfaef08b1…0696
0x34b655…2a6f
14 touches
21 conflicts
0xac2a0273…721b
0x34b655…2a6f
12 touches
15 conflicts
0xefcdf197…96a2
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…0002
0x04fdea…47d7
8 touches
6 conflicts
0xa29182a1…c12c
0x34b655…2a6f
8 touches
6 conflicts
0xb4e0a934…5fc7
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
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
36 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity