← previous blocknext block →recent activity
Analyzing
Block #86,815,444
23 transactions · 18 stateful · 2026-07-10 09:53:52 UTC
Parallelism
83/100
Blocked
61%
Avg conflicts / tx
0.87
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,815,444 · 23 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
2w03w14w27w08w19w210w311w013w114w315w216w317w121w022w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0x76d1e78d…7877
0x40c49f…2af0
8 touches
6 conflicts
0x00000000…003d
0x40c49f…2af0
8 touches
6 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x5d46e6a0…5ed9
0x40c49f…2af0
6 touches
3 conflicts
0xfc404689…bd5b
0x40c49f…2af0
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x33bd5ec4…af53
0xa6afd3…d132
6 touches
3 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 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity