← previous blocknext block →recent activity
Analyzing
Block #86,951,800
31 transactions · 26 stateful · 2026-07-11 01:05:32 UTC
Parallelism
81/100
Blocked
58%
Avg conflicts / tx
1.1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,951,800 · 31 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w26w38w09w111w212w013w114w215w316w417w518w222w424w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…003d
0xa6afd3…d132
10 touches
10 conflicts
0xc7a15219…7745
0xa6afd3…d132
10 touches
10 conflicts
0xef65bff3…7c9d
0x2a68ba…90c5
8 touches
6 conflicts
0xdf708ee7…1fcf
0xc8689a…ee79
8 touches
6 conflicts
0xdb067026…9eb8
0x69df8a…6292
8 touches
6 conflicts
0xb05cd4f5…73d0
0x69df8a…6292
8 touches
6 conflicts
0x33bd5ec4…af53
0xa6afd3…d132
8 touches
6 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
15 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity