← previous blocknext block →recent activity
Analyzing
Block #85,190,920
15 transactions · 14 stateful · 2026-07-02 21:13:58 UTC
Parallelism
53/100
Blocked
43%
Avg conflicts / tx
1.13
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #85,190,920 · 15 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
2w03w14w25w36w411w012w513w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
10 touches
10 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
10 touches
10 conflicts
0x06aed19e…ca57
0x34b655…2a6f
8 touches
6 conflicts
0x1bfc029c…f91e
0x34b655…2a6f
8 touches
6 conflicts
0x8e507257…71c1
0x34b655…2a6f
8 touches
6 conflicts
0xa1571d54…ae41
0x34b655…2a6f
8 touches
6 conflicts
0xa91e0a92…0322
0x34b655…2a6f
8 touches
6 conflicts
0xbbb9fa77…d121
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
10 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity