← previous blocknext block →recent activity
Analyzing
Block #87,709,110
56 transactions · 37 stateful · 2026-07-14 13:30:04 UTC
Parallelism
68/100
Blocked
68%
Avg conflicts / tx
2.95
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #87,709,110 · 56 txs across 18 waves · depth 18
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
wave w17
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w17w08w19w010w111w212w313w414w015w130w031w132w233w334w435w536w637w738w839w951w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
34 touches
136 conflicts
0x889d5e90…929a
0x2a68ba…90c5
10 touches
10 conflicts
0x039c2f44…9ac7
0x34b655…2a6f
8 touches
6 conflicts
0x0dd44476…ef40
0x34b655…2a6f
8 touches
6 conflicts
0x21db75f9…31d3
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0x3d381afb…8207
0x34b655…2a6f
8 touches
6 conflicts
0x507ccc1a…57de
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
136 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity