← previous blocknext block →recent activity
Analyzing
Block #85,523,853
9 transactions · 8 stateful · 2026-07-04 10:11:13 UTC
Parallelism
78/100
Blocked
13%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,523,853 · 9 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
1w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x689d5e98…d068
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00469641…891e
0x34b655…2a6f
2 touches
0 conflicts
0x152cc7e9…0b73
0x34b655…2a6f
2 touches
0 conflicts
0x3923cd2c…e6d3
0x34b655…2a6f
2 touches
0 conflicts
0x4c2d33f9…dd4b
0x34b655…2a6f
2 touches
0 conflicts
0x6187493c…c8c6
0x34b655…2a6f
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity