← previous blocknext block →recent activity
Analyzing
Block #85,124,836
55 transactions · 37 stateful · 2026-07-02 13:53:38 UTC
Parallelism
87/100
Blocked
51%
Avg conflicts / tx
0.98
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #85,124,836 · 55 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
1w02w13w24w35w46w519w520w621w631w642w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
14 touches
21 conflicts
0xe61c6b34…6da7
0xd32edf…ff58
13 touches
21 conflicts
0x25de453d…9573
0x34b655…2a6f
8 touches
6 conflicts
0x22d3c767…e4d1
0x34b655…2a6f
8 touches
6 conflicts
0x3a192eef…3c7f
0x34b655…2a6f
8 touches
6 conflicts
0x4f4bdabd…ffba
0x34b655…2a6f
8 touches
6 conflicts
0x656bd53e…af4e
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
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