← previous blocknext block →recent activity
Analyzing
Block #85,125,824
18 transactions · 17 stateful · 2026-07-02 14:00:14 UTC
Parallelism
78/100
Blocked
53%
Avg conflicts / tx
0.67
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,125,824 · 18 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w14w15w06w07w18w29w311w113w215w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe47478a3…a058
0x34b655…2a6f
8 touches
6 conflicts
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0x03fb27fd…0c06
0x34b655…2a6f
8 touches
6 conflicts
0x12ef5e13…31a6
0x34b655…2a6f
8 touches
6 conflicts
0x14d7d912…af17
0x34b655…2a6f
8 touches
6 conflicts
0x159b8597…48a4
0x34b655…2a6f
8 touches
6 conflicts
0x922c7ebd…6600
0xc8689a…ee79
8 touches
6 conflicts
0x6412ffc8…2167
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
6 conflicts on slot 0xe47478a3e7…67a058
Audit this contract →
← previous block·next block →recent activity