← previous blocknext block →recent activity
Analyzing
Block #85,169,214
12 transactions · 9 stateful · 2026-07-02 18:49:26 UTC
Parallelism
83/100
Blocked
22%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,169,214 · 12 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
1w03w06w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x02c4bb0f…f2c8
0x34b655…2a6f
4 touches
1 conflict
0x14fe1598…d0ba
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xd06fb4dc…5204
0x34b655…2a6f
4 touches
1 conflict
0x181732de…9796
0x34b655…2a6f
2 touches
0 conflicts
0x1c287db3…e562
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 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity