← previous blocknext block →recent activity
Analyzing
Block #87,577,596
48 transactions · 40 stateful · 2026-07-13 22:50:39 UTC
Parallelism
71/100
Blocked
73%
Avg conflicts / tx
2.1
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #87,577,596 · 48 txs across 14 waves · depth 14
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w15w26w19w010w111w012w118w019w120w221w322w423w524w228w629w733w734w835w936w137w238w341w842w945w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
14 touches
21 conflicts
0xac2a0273…721b
0x34b655…2a6f
12 touches
15 conflicts
0x54b193ad…c830
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…0001
0xc1ff9f…b0fc
12 touches
15 conflicts
0x737acb78…fce8
0x34b655…2a6f
10 touches
10 conflicts
0xe2607c11…8fa7
0x34b655…2a6f
10 touches
10 conflicts
0x30faf03c…78b1
0x34b655…2a6f
10 touches
10 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