← previous blocknext block →recent activity
Analyzing
Block #85,158,627
10 transactions · 9 stateful · 2026-07-02 17:39:01 UTC
Parallelism
60/100
Blocked
33%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,158,627 · 10 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
6w07w18w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x159b8597…48a4
0x34b655…2a6f
4 touches
1 conflict
0x2406ccf7…c1cb
0x34b655…2a6f
4 touches
1 conflict
0x83878baf…4124
0x34b655…2a6f
4 touches
1 conflict
0x7e3e6d2d…c5d8
0x065c9d…c394
2 touches
0 conflicts
0xb6a31785…afa4
0x065c9d…c394
2 touches
0 conflicts
0xb925ac63…4f3c
0x065c9d…c394
2 touches
0 conflicts
0xdfc1cbb6…fb88
0x065c9d…c394
2 touches
0 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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity