← previous blocknext block →recent activity
Analyzing
Block #85,128,800
36 transactions · 32 stateful · 2026-07-02 14:20:08 UTC
Parallelism
78/100
Blocked
72%
Avg conflicts / tx
1.89
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #85,128,800 · 36 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w16w27w38w49w510w624w225w626w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
16 touches
28 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
14 touches
21 conflicts
0x00000000…003d
0xa6afd3…d132
10 touches
10 conflicts
0x66c5e348…51d0
0xa6afd3…d132
10 touches
10 conflicts
0xef65bff3…7c9d
0x2a68ba…90c5
8 touches
6 conflicts
0x4384dd01…4f99
0x34b655…2a6f
8 touches
6 conflicts
0x1b3114cd…5e2d
0xa6afd3…d132
8 touches
6 conflicts
0xdf708ee7…1fcf
0xc8689a…ee79
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
28 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity