← previous blocknext block →recent activity
Analyzing
Block #87,709,918
46 transactions · 43 stateful · 2026-07-14 13:35:29 UTC
Parallelism
67/100
Blocked
56%
Avg conflicts / tx
1.3
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #87,709,918 · 46 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
1w02w13w24w06w07w08w19w010w011w112w113w216w017w118w220w321w422w523w627w728w830w135w138w141w1142w1243w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0x309f5473…78aa
0x34b655…2a6f
8 touches
6 conflicts
0x85a88798…f85e
0x34b655…2a6f
6 touches
3 conflicts
0x94e7f277…471b
0x34b655…2a6f
6 touches
3 conflicts
0xa84ca715…9c73
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
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
15 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity