← previous blocknext block →recent activity
Analyzing
Block #85,141,773
34 transactions · 34 stateful · 2026-07-02 15:46:46 UTC
Parallelism
79/100
Blocked
62%
Avg conflicts / tx
1.47
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #85,141,773 · 34 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w07w18w09w010w111w012w113w214w315w416w517w621w422w224w325w527w129w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
14 touches
21 conflicts
0xa9988419…9f45
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x12c6929d…e7db
0x34b655…2a6f
8 touches
6 conflicts
0xd60d2a7f…dec1
0xd32edf…ff58
7 touches
6 conflicts
0xc0f29314…17f8
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 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