← previous blocknext block →recent activity
Analyzing
Block #87,504,298
46 transactions · 36 stateful · 2026-07-13 14:39:41 UTC
Parallelism
63/100
Blocked
61%
Avg conflicts / tx
2.26
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #87,504,298 · 46 txs across 17 waves · depth 17
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
wave w14
wave w15
wave w16
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w08w09w110w220w221w325w726w827w930w1132w1235w1337w138w1442w1543w16
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
18 touches
36 conflicts
0x734ee320…caae
0x34b655…2a6f
16 touches
28 conflicts
0x1d946063…ba90
0x34b655…2a6f
14 touches
21 conflicts
0x3a6290da…e683
0x34b655…2a6f
10 touches
10 conflicts
0xf06ab8d8…3589
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xa144b131…5320
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
36 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity