← previous blocknext block →recent activity
Analyzing
Block #85,250,881
17 transactions · 15 stateful · 2026-07-03 03:53:27 UTC
Parallelism
76/100
Blocked
27%
Avg conflicts / tx
0.53
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,250,881 · 17 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
4w05w06w09w110w011w115w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x27f2c756…0ffc
0x34b655…2a6f
8 touches
6 conflicts
0x4233ce00…6a67
0x34b655…2a6f
6 touches
3 conflicts
0xeff94efd…f7d7
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xcdc1731c…b91a
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
6 conflicts on slot 0x27f2c75698…900ffc
Audit this contract →
← previous block·next block →recent activity