← previous blocknext block →recent activity
Analyzing
Block #85,169,143
54 transactions · 39 stateful · 2026-07-02 18:48:58 UTC
Parallelism
81/100
Blocked
64%
Avg conflicts / tx
1.3
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #85,169,143 · 54 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w17w09w110w212w328w237w445w346w448w351w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
14 touches
21 conflicts
0x00000000…003d
0xa6afd3…d132
10 touches
10 conflicts
0x2c8bf7d9…3cc7
0xc8689a…ee79
10 touches
10 conflicts
0x301e1c77…9e30
0x34b655…2a6f
10 touches
10 conflicts
0x1ee44d08…7262
0x34b655…2a6f
10 touches
10 conflicts
0x22d3c767…e4d1
0x34b655…2a6f
10 touches
10 conflicts
0xd06fb4dc…5204
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
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
21 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity