← previous blocknext block →recent activity
Analyzing
Block #87,704,886
78 transactions · 60 stateful · 2026-07-14 13:01:47 UTC
Parallelism
71/100
Blocked
82%
Avg conflicts / tx
4.55
Longest chain
23 deep
Execution timeline
did this block parallelize well?
view
block #87,704,886 · 78 txs across 23 waves · depth 23
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
wave w18
wave w19
wave w20
wave w21
wave w22
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w112w215w516w618w720w821w964w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
46 touches
253 conflicts
0x767799cd…f423
0xc8689a…ee79
22 touches
55 conflicts
0xe7ceda84…1a3e
0x34b655…2a6f
22 touches
55 conflicts
0x15c9b5bf…f732
0x34b655…2a6f
22 touches
55 conflicts
0xab5ba139…ea6f
0x34b655…2a6f
22 touches
55 conflicts
0x7fd53511…8f76
0x34b655…2a6f
22 touches
55 conflicts
0xce40a269…92eb
0x34b655…2a6f
22 touches
55 conflicts
0xa2f78844…cd94
0xd32edf…ff58
21 touches
55 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
253 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity