← previous blocknext block →recent activity
Analyzing
Block #85,126,222
55 transactions · 39 stateful · 2026-07-02 14:02:54 UTC
Parallelism
71/100
Blocked
69%
Avg conflicts / tx
2.85
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #85,126,222 · 55 txs across 16 waves · depth 16
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w17w210w313w416w524w025w126w227w328w429w530w631w740w144w246w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
32 touches
120 conflicts
0x3a192eef…3c7f
0x34b655…2a6f
22 touches
55 conflicts
0x4f4bdabd…ffba
0x34b655…2a6f
22 touches
55 conflicts
0xac2a0273…721b
0x34b655…2a6f
22 touches
55 conflicts
0x2c8bf7d9…3cc7
0xc8689a…ee79
22 touches
55 conflicts
0x2de2656d…5bbc
0x34b655…2a6f
18 touches
36 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
12 touches
15 conflicts
0xdb067026…9eb8
0x69df8a…6292
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
120 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity