← previous blocknext block →recent activity
Analyzing
Block #87,704,125
74 transactions · 48 stateful · 2026-07-14 12:56:42 UTC
Parallelism
74/100
Blocked
69%
Avg conflicts / tx
2.35
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #87,704,125 · 74 txs across 19 waves · depth 19
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
wave w16
wave w17
wave w18
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w423w524w625w726w859w963w566w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
24 touches
66 conflicts
0xdac4c045…3f0e
0xd32edf…ff58
19 touches
45 conflicts
0xac2a0273…721b
0x34b655…2a6f
12 touches
15 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
12 touches
15 conflicts
0x8fe37a3f…4c89
0x34b655…2a6f
12 touches
15 conflicts
0x4f51d069…d0b4
0x34b655…2a6f
10 touches
10 conflicts
0xeeaba9d3…b491
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…003d
0xa6afd3…d132
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
66 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity