← previous blocknext block →recent activity
Analyzing
Block #87,718,547
22 transactions · 18 stateful · 2026-07-14 14:33:22 UTC
Parallelism
64/100
Blocked
56%
Avg conflicts / tx
1.59
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #87,718,547 · 22 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w26w37w48w59w610w716w220w121w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
16 touches
28 conflicts
0x59ed335a…d2f3
0x34b655…2a6f
8 touches
6 conflicts
0x074a2e51…c2f2
0x34b655…2a6f
8 touches
6 conflicts
0xa6c9a33e…d839
0x34b655…2a6f
8 touches
6 conflicts
0x0ba865dd…a249
0x34b655…2a6f
8 touches
6 conflicts
0x7525206c…fbd5
0x34b655…2a6f
6 touches
3 conflicts
0x807bf45f…5016
0x34b655…2a6f
6 touches
3 conflicts
0x5b145de0…367c
0xc8689a…ee79
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
28 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity