← previous blocknext block →recent activity
Analyzing
Block #85,250,401
19 transactions · 19 stateful · 2026-07-03 03:50:15 UTC
Parallelism
68/100
Blocked
47%
Avg conflicts / tx
0.89
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #85,250,401 · 19 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
1w02w13w24w05w16w07w08w19w210w314w415w117w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x95847041…2d63
0x34b655…2a6f
10 touches
10 conflicts
0x3230277c…ef39
0xc8689a…ee79
8 touches
6 conflicts
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0x83f3d320…fb59
0x34b655…2a6f
8 touches
6 conflicts
0x8d24fe06…31f4
0x34b655…2a6f
8 touches
6 conflicts
0x95d8cf85…13b3
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0x08e8f2c9…a11a
0x34b655…2a6f
6 touches
3 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 0x95847041f0…322d63
Audit this contract →
← previous block·next block →recent activity