← previous blocknext block →recent activity
Analyzing
Block #87,713,866
50 transactions · 43 stateful · 2026-07-14 14:01:55 UTC
Parallelism
80/100
Blocked
67%
Avg conflicts / tx
2.06
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #87,713,866 · 50 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w26w38w010w316w317w418w530w644w445w446w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
14 touches
21 conflicts
0x375745db…a53d
0xd32edf…ff58
13 touches
21 conflicts
0xea02471d…1542
0x34b655…2a6f
10 touches
10 conflicts
0xbf78ee7f…e7fd
0x34b655…2a6f
10 touches
10 conflicts
0x94ba9c4a…41d8
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xe1c784c4…ac83
0x34b655…2a6f
8 touches
6 conflicts
0xe6a34ca2…4075
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
21 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity