← previous blocknext block →recent activity
Analyzing
Block #87,708,542
40 transactions · 33 stateful · 2026-07-14 13:26:16 UTC
Parallelism
77/100
Blocked
70%
Avg conflicts / tx
1.93
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #87,708,542 · 40 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w47w58w625w728w531w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
16 touches
28 conflicts
0x020de0ee…9a35
0xd32edf…ff58
11 touches
15 conflicts
0xa3a621f8…75a2
0x34b655…2a6f
10 touches
10 conflicts
0x889d5e90…929a
0x2a68ba…90c5
10 touches
10 conflicts
0x00000000…002d
0x1b6862…e19c
8 touches
6 conflicts
0xd5b10148…e636
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
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