← previous blocknext block →recent activity
Analyzing
Block #85,168,911
18 transactions · 16 stateful · 2026-07-02 18:47:25 UTC
Parallelism
67/100
Blocked
38%
Avg conflicts / tx
0.94
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #85,168,911 · 18 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w19w011w012w113w215w316w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x74462c1e…84f3
0x34b655…2a6f
6 touches
3 conflicts
0x37674bd8…8f35
0x34b655…2a6f
6 touches
3 conflicts
0x7fffd49d…772a
0x34b655…2a6f
6 touches
3 conflicts
0x207420c2…5626
0x34b655…2a6f
6 touches
3 conflicts
0x2406ccf7…c1cb
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0x04fdea…47d7
4 touches
1 conflict
0x845ec8b0…c1af
0x34b655…2a6f
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
15 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity