← previous blocknext block →recent activity
Analyzing
Block #85,180,346
13 transactions · 9 stateful · 2026-07-02 20:03:34 UTC
Parallelism
85/100
Blocked
22%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,180,346 · 13 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w07w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x53b4ef2b…8a05
0x34b655…2a6f
4 touches
1 conflict
0xaf9d1409…c186
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x8ad140a9…e449
0x065c9d…c394
2 touches
0 conflicts
0xc6f032f6…3357
0x065c9d…c394
2 touches
0 conflicts
0xcf91e5b1…5217
0x065c9d…c394
2 touches
0 conflicts
0xf8f6033b…09d7
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
2 touches
0 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
1 conflict on slot 0x53b4ef2b77…528a05
Audit this contract →
← previous block·next block →recent activity