← previous blocknext block →recent activity
Analyzing
Block #87,715,392
36 transactions · 35 stateful · 2026-07-14 14:12:10 UTC
Parallelism
58/100
Blocked
66%
Avg conflicts / tx
3.17
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #87,715,392 · 36 txs across 15 waves · depth 15
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w18w09w110w211w312w413w514w615w718w119w220w722w224w829w930w1033w1334w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
16 touches
28 conflicts
0x8b818135…eff8
0x34b655…2a6f
14 touches
21 conflicts
0xbf78ee7f…e7fd
0x34b655…2a6f
14 touches
21 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
12 touches
15 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x22388e8d…45d7
0x34b655…2a6f
10 touches
10 conflicts
0x2d8a87f4…9991
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity