← previous blocknext block →recent activity
Analyzing
Block #87,714,219
35 transactions · 32 stateful · 2026-07-14 14:04:17 UTC
Parallelism
60/100
Blocked
66%
Avg conflicts / tx
2.29
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #87,714,219 · 35 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
1w02w13w24w35w06w110w111w212w316w417w418w519w620w721w823w324w929w1032w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x92385428…6941
0x34b655…2a6f
16 touches
28 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
16 touches
28 conflicts
0x7e5ea60a…c4a4
0x34b655…2a6f
12 touches
15 conflicts
0x93b6fab0…09d6
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…00c9
0x34b655…2a6f
12 touches
15 conflicts
0x7e5ea60a…c4a2
0x34b655…2a6f
12 touches
15 conflicts
0x7e5ea60a…c4b2
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4a3
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
28 conflicts on slot 0x92385428ad…dc6941
Audit this contract →
← previous block·next block →recent activity