← previous blocknext block →recent activity
Analyzing
Block #87,710,681
35 transactions · 32 stateful · 2026-07-14 13:40:35 UTC
Parallelism
71/100
Blocked
69%
Avg conflicts / tx
2.23
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #87,710,681 · 35 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w59w010w115w116w221w223w425w627w729w832w833w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0f6666e6…f280
0x34b655…2a6f
14 touches
21 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
12 touches
15 conflicts
0x618b40d4…00b3
0xd32edf…ff58
11 touches
15 conflicts
0x00000000…001d
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…002d
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0xdb95e18e…c73c
0x1b6862…e19c
10 touches
10 conflicts
0x0733be30…112f
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
21 conflicts on slot 0x0f6666e640…06f280
Audit this contract →
← previous block·next block →recent activity