← previous blocknext block →recent activity
Analyzing
Block #87,758,994
28 transactions · 25 stateful · 2026-07-14 19:03:54 UTC
Parallelism
75/100
Blocked
48%
Avg conflicts / tx
1.39
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,758,994 · 28 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w26w37w48w514w117w219w320w424w525w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
12 touches
15 conflicts
0xd99b3b64…1c95
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…003d
0x40c49f…2af0
10 touches
10 conflicts
0xf3fbc9b8…ab58
0x34b655…2a6f
10 touches
10 conflicts
0xca18c58e…cede
0x34b655…2a6f
8 touches
6 conflicts
0xced67f0c…5126
0x34b655…2a6f
8 touches
6 conflicts
0x5170a218…3a84
0xc8689a…ee79
8 touches
6 conflicts
0x20ff72d4…5971
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
15 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity