← previous blocknext block →recent activity
Analyzing
Block #87,589,561
56 transactions · 43 stateful · 2026-07-14 00:10:40 UTC
Parallelism
73/100
Blocked
63%
Avg conflicts / tx
1.7
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #87,589,561 · 56 txs across 15 waves · depth 15
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w07w18w09w111w012w120w021w122w223w324w425w526w630w131w133w835w236w137w239w240w343w344w445w450w1051w1152w1254w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
16 touches
28 conflicts
0x69ce640b…884a
0x34b655…2a6f
12 touches
15 conflicts
0xac2a0273…721b
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…003d
0xa6afd3…d132
10 touches
10 conflicts
0x689d5e98…d068
0x34b655…2a6f
10 touches
10 conflicts
0xa534ab65…4ee7
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
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