← previous blocknext block →recent activity
Analyzing
Block #85,873,491
14 transactions · 13 stateful · 2026-07-06 01:00:44 UTC
Parallelism
71/100
Blocked
23%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,873,491 · 14 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
5w06w18w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xafd867b7…2b2d
0x34b655…2a6f
8 touches
6 conflicts
0xafd867b7…2b2e
0x34b655…2a6f
6 touches
3 conflicts
0x6c39ccdd…031c
0x34b655…2a6f
4 touches
1 conflict
0x7a51f6c0…1c43
0x34b655…2a6f
4 touches
1 conflict
0x03ef1aec…f7ea
0x34b655…2a6f
2 touches
0 conflicts
0x1e7e4246…4872
0x34b655…2a6f
2 touches
0 conflicts
0x28287367…f0f5
0x34b655…2a6f
2 touches
0 conflicts
0x35563c03…7689
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
6 conflicts on slot 0xafd867b7ed…d92b2d
Audit this contract →
← previous block·next block →recent activity