← previous blocknext block →recent activity
Analyzing
Block #86,812,084
20 transactions · 17 stateful · 2026-07-10 09:31:25 UTC
Parallelism
80/100
Blocked
41%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,812,084 · 20 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
1w02w13w25w210w011w114w215w316w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0xa2894f3e…621f
0x40c49f…2af0
6 touches
3 conflicts
0x2b54cadb…4425
0xd18b7e…414b
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xa100c256…fb30
0x34b655…2a6f
6 touches
3 conflicts
0x9fc8b97d…96da
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…0002
0x614b85…a284
4 touches
1 conflict
0x00000000…0004
0x614b85…a284
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