← previous blocknext block →recent activity
Analyzing
Block #87,711,860
50 transactions · 38 stateful · 2026-07-14 13:48:28 UTC
Parallelism
72/100
Blocked
68%
Avg conflicts / tx
2.16
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #87,711,860 · 50 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
1w05w07w18w012w113w014w121w022w123w224w325w426w527w628w729w130w831w935w237w138w1042w243w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
24 touches
66 conflicts
0xbf78ee7f…e7fd
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x173337fe…f0af
0x34b655…2a6f
8 touches
6 conflicts
0xa883fad7…722c
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x2385516f…eca5
0x34b655…2a6f
8 touches
6 conflicts
0xd9072021…db76
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
66 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity