← previous blocknext block →recent activity
Analyzing
Block #87,712,522
49 transactions · 39 stateful · 2026-07-14 13:52:54 UTC
Parallelism
73/100
Blocked
69%
Avg conflicts / tx
1.98
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #87,712,522 · 49 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
3w04w15w27w08w19w212w015w016w121w022w123w224w325w426w527w629w230w131w234w537w738w240w341w346w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
16 touches
28 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…00c9
0x34b655…2a6f
10 touches
10 conflicts
0x6a1604d1…3e8a
0x34b655…2a6f
10 touches
10 conflicts
0x92385428…6941
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
8 touches
6 conflicts
0x93b6fab0…09d6
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
28 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity