← previous blocknext block →recent activity
Analyzing
Block #86,957,230
11 transactions · 11 stateful · 2026-07-11 01:41:50 UTC
Parallelism
64/100
Blocked
45%
Avg conflicts / tx
0.82
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,957,230 · 11 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
3w04w15w26w38w09w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0xb7dbe79a…4499
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x216ffe66…1f94
0x34b655…2a6f
4 touches
1 conflict
0x24e3bf88…17bf
0x34b655…2a6f
4 touches
1 conflict
0x352cdf9c…2863
0x34b655…2a6f
4 touches
1 conflict
0x44231245…5442
0x34b655…2a6f
4 touches
1 conflict
0x45c033be…0aad
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
6 conflicts on slot 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity