← previous blocknext block →recent activity
Analyzing
Block #85,920,630
18 transactions · 17 stateful · 2026-07-06 06:14:47 UTC
Parallelism
83/100
Blocked
41%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,920,630 · 18 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w06w18w19w215w116w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xafd867b7…2b2e
0x34b655…2a6f
6 touches
3 conflicts
0x10a2bd5d…ad6d
0x8d1565…6723
6 touches
3 conflicts
0x00000000…000a
0x90c374…be45
6 touches
3 conflicts
0x00000000…000b
0x90c374…be45
6 touches
3 conflicts
0x33e3dcdd…1f1f
0x34b655…2a6f
4 touches
1 conflict
0x49444a23…eec2
0x34b655…2a6f
4 touches
1 conflict
0x5e782d17…5318
0x34b655…2a6f
4 touches
1 conflict
0x7e4b5149…c444
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
3 conflicts on slot 0xafd867b7ed…d92b2e
Audit this contract →
← previous block·next block →recent activity