← previous blocknext block →recent activity
Analyzing
Block #85,027,700
38 transactions · 33 stateful · 2026-07-02 03:03:54 UTC
Parallelism
68/100
Blocked
70%
Avg conflicts / tx
2.42
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #85,027,700 · 38 txs across 12 waves · depth 12
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w27w38w49w510w611w712w813w630w931w1032w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
18 touches
36 conflicts
0x00000000…003d
0xa6afd3…d132
16 touches
28 conflicts
0xe4afaa2f…3b69
0xa6afd3…d132
16 touches
28 conflicts
0x7b9a42f7…7b88
0xa6afd3…d132
14 touches
21 conflicts
0xc9a3f1a3…84d0
0xd32edf…ff58
13 touches
21 conflicts
0x00000000…0012
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0013
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0015
0x1b6862…e19c
12 touches
15 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 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity