← previous blocknext block →recent activity
Analyzing
Block #87,518,615
48 transactions · 42 stateful · 2026-07-13 16:15:36 UTC
Parallelism
75/100
Blocked
71%
Avg conflicts / tx
2.21
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #87,518,615 · 48 txs across 12 waves · depth 12
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w27w18w210w311w012w113w014w117w018w119w220w321w422w523w624w730w533w634w735w838w341w444w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
18 touches
36 conflicts
0x00000000…0001
0xc1ff9f…b0fc
16 touches
28 conflicts
0x4cabb80a…46bf
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…00c9
0x34b655…2a6f
12 touches
15 conflicts
0x3d4c0233…20a5
0x34b655…2a6f
10 touches
10 conflicts
0x52d2a422…f1ea
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4a3
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4a4
0x34b655…2a6f
10 touches
10 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
36 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity