← previous blocknext block →recent activity
Analyzing
Block #85,142,380
14 transactions · 13 stateful · 2026-07-02 15:50:48 UTC
Parallelism
64/100
Blocked
38%
Avg conflicts / tx
0.64
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,142,380 · 14 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w05w16w28w110w011w312w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x305e6edb…89b1
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x43e2eda1…396f
0x34b655…2a6f
4 touches
1 conflict
0x7ae63663…9d94
0x34b655…2a6f
4 touches
1 conflict
0x97c67486…27fe
0x34b655…2a6f
4 touches
1 conflict
0xa2cc62d4…69f6
0x34b655…2a6f
4 touches
1 conflict
0xa62c47db…5ec8
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 0x305e6edb9c…d189b1
Audit this contract →
← previous block·next block →recent activity