← previous blocknext block →recent activity
Analyzing
Block #87,711,977
41 transactions · 34 stateful · 2026-07-14 13:49:15 UTC
Parallelism
68/100
Blocked
68%
Avg conflicts / tx
1.95
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #87,711,977 · 41 txs across 13 waves · depth 13
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w05w16w07w18w09w110w011w114w115w216w317w418w519w620w721w822w923w1032w333w135w237w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
20 touches
45 conflicts
0x2385516f…eca5
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xbc66586e…20fe
0x34b655…2a6f
8 touches
6 conflicts
0x8fe37a3f…4c89
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0xa558e115…fc88
0x34b655…2a6f
6 touches
3 conflicts
0xa863a526…9995
0x34b655…2a6f
6 touches
3 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
45 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity