← previous blocknext block →recent activity
Analyzing
Block #85,138,448
21 transactions · 19 stateful · 2026-07-02 15:24:34 UTC
Parallelism
67/100
Blocked
37%
Avg conflicts / tx
0.86
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #85,138,448 · 21 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
1w05w08w110w113w214w315w417w518w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x43e2eda1…396f
0x34b655…2a6f
8 touches
6 conflicts
0x12c6929d…e7db
0x34b655…2a6f
4 touches
1 conflict
0x4f00a21e…db6c
0x34b655…2a6f
4 touches
1 conflict
0x9c233126…0be7
0x34b655…2a6f
4 touches
1 conflict
0xab3a7dc6…0ed8
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity