← previous blocknext block →recent activity
Analyzing
Block #86,608,848
45 transactions · 39 stateful · 2026-07-09 10:52:53 UTC
Parallelism
69/100
Blocked
69%
Avg conflicts / tx
2.49
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #86,608,848 · 45 txs across 14 waves · depth 14
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w15w26w27w38w09w111w012w113w214w315w416w517w618w719w820w921w1022w1126w131w332w434w240w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
24 touches
66 conflicts
0x64aaadbf…f9f3
0x34b655…2a6f
18 touches
36 conflicts
0x5f72d58f…c445
0x34b655…2a6f
16 touches
28 conflicts
0xd1ec0dfd…ccc0
0xc8689a…ee79
16 touches
28 conflicts
0x1e48811e…2e39
0x34b655…2a6f
16 touches
28 conflicts
0x890eac6e…1c0d
0x34b655…2a6f
16 touches
28 conflicts
0x9e3f5c49…42e1
0x34b655…2a6f
16 touches
28 conflicts
0xaba6578d…bd48
0x34b655…2a6f
16 touches
28 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
66 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity