← previous blocknext block →recent activity
Analyzing
Block #86,630,913
23 transactions · 18 stateful · 2026-07-09 13:20:12 UTC
Parallelism
83/100
Blocked
39%
Avg conflicts / tx
0.48
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,630,913 · 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
1w02w17w08w09w111w212w313w221w122w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa08f40b2…9a93
0x34b655…2a6f
6 touches
3 conflicts
0xfc578b53…9b1f
0xa6afd3…d132
6 touches
3 conflicts
0x9da6e429…074d
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…003d
0x851145…3f07
6 touches
3 conflicts
0x02991b41…19e6
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0xd98b3c10…67b8
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 0xa08f40b255…099a93
Audit this contract →
← previous block·next block →recent activity