← previous blocknext block →recent activity
Analyzing
Block #87,880,286
67 transactions · 40 stateful · 2026-07-15 08:35:14 UTC
Parallelism
76/100
Blocked
70%
Avg conflicts / tx
1.39
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #87,880,286 · 67 txs across 16 waves · depth 16
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
wave w15
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w07w08w19w210w311w112w213w326w027w128w229w330w431w532w637w241w343w445w646w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…003d
0x40c49f…2af0
10 touches
10 conflicts
0xc88f593e…5d93
0x336ed4…c59c
8 touches
6 conflicts
0x428b6e5b…8909
0x34b655…2a6f
8 touches
6 conflicts
0x4acbdbcf…a8c6
0x34b655…2a6f
8 touches
6 conflicts
0x64aaadbf…f9f3
0x34b655…2a6f
8 touches
6 conflicts
0x6ba1094f…8384
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