← previous blocknext block →recent activity
Analyzing
Block #87,918,365
51 transactions · 39 stateful · 2026-07-15 12:49:55 UTC
Parallelism
74/100
Blocked
69%
Avg conflicts / tx
1.65
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #87,918,365 · 51 txs across 13 waves · depth 13
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w27w08w111w212w013w114w218w019w123w124w225w326w427w532w733w836w237w139w942w343w346w1049w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
16 touches
28 conflicts
0xa08f40b2…9a93
0x34b655…2a6f
10 touches
10 conflicts
0xc948dbdc…199a
0x34b655…2a6f
10 touches
10 conflicts
0x17332fb4…cb06
0x34b655…2a6f
10 touches
10 conflicts
0x1941b441…5889
0x34b655…2a6f
10 touches
10 conflicts
0x06a27525…f082
0x34b655…2a6f
8 touches
6 conflicts
0x52b477bc…7ccf
0x34b655…2a6f
8 touches
6 conflicts
0x7b6111f6…ed1b
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
28 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity