← previous blocknext block →recent activity
Analyzing
Block #87,625,112
40 transactions · 31 stateful · 2026-07-14 04:08:24 UTC
Parallelism
60/100
Blocked
68%
Avg conflicts / tx
2.38
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #87,625,112 · 40 txs across 16 waves · depth 16
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
wave w14
wave w15
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w111w012w113w214w315w416w517w618w725w1126w1227w329w1330w431w538w1439w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
22 touches
55 conflicts
0x4c188934…158e
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…003d
0x40c49f…2af0
10 touches
10 conflicts
0x08330b36…ae29
0x34b655…2a6f
10 touches
10 conflicts
0x4f4a7ac3…021c
0x34b655…2a6f
8 touches
6 conflicts
0x8981596f…d14a
0x34b655…2a6f
8 touches
6 conflicts
0x9599eb41…b5d6
0x34b655…2a6f
8 touches
6 conflicts
0xc6ed530e…fa7d
0x34b655…2a6f
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
55 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity