← previous blocknext block →recent activity
Analyzing
Block #87,517,823
48 transactions · 39 stateful · 2026-07-13 16:10:14 UTC
Parallelism
67/100
Blocked
64%
Avg conflicts / tx
2.08
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #87,517,823 · 48 txs across 16 waves · depth 16
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w39w312w013w122w323w424w525w626w728w829w931w1032w433w1034w535w236w339w1140w1243w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
16 touches
28 conflicts
0x69ce640b…884a
0x34b655…2a6f
14 touches
21 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x89822ef8…5628
0x34b655…2a6f
10 touches
10 conflicts
0x99ee776a…053a
0x34b655…2a6f
10 touches
10 conflicts
0xa535ecc7…c0e0
0x34b655…2a6f
10 touches
10 conflicts
0xac2a0273…721b
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
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