← previous blocknext block →recent activity
Analyzing
Block #85,142,499
11 transactions · 11 stateful · 2026-07-02 15:51:36 UTC
Parallelism
64/100
Blocked
27%
Avg conflicts / tx
0.45
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,142,499 · 11 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
2w08w19w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x5b353877…605d
0x34b655…2a6f
4 touches
1 conflict
0xc57747c0…99d1
0x34b655…2a6f
4 touches
1 conflict
0xdd3e925c…23ac
0x34b655…2a6f
4 touches
1 conflict
0x43e2eda1…396f
0x34b655…2a6f
4 touches
1 conflict
0x1c25cccc…bb41
0x34b655…2a6f
2 touches
0 conflicts
0x1ee949ae…7e8f
0x34b655…2a6f
2 touches
0 conflicts
0x207d2870…e720
0x34b655…2a6f
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
3 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity