← previous blocknext block →recent activity
Analyzing
Block #87,715,116
34 transactions · 31 stateful · 2026-07-14 14:10:18 UTC
Parallelism
68/100
Blocked
55%
Avg conflicts / tx
1.71
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #87,715,116 · 34 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w15w06w19w210w311w412w513w616w317w418w519w624w729w831w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
12 touches
15 conflicts
0xa779293b…5e59
0x34b655…2a6f
10 touches
10 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x93b6fab0…09d6
0x34b655…2a6f
10 touches
10 conflicts
0x9354a4d0…be91
0x34b655…2a6f
10 touches
10 conflicts
0x077d58c3…8ed7
0x34b655…2a6f
8 touches
6 conflicts
0xa6389d47…9a28
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
15 conflicts on slot 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity