← previous blocknext block →recent activity
Analyzing
Block #87,723,920
52 transactions · 44 stateful · 2026-07-14 15:09:18 UTC
Parallelism
73/100
Blocked
66%
Avg conflicts / tx
2.92
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #87,723,920 · 52 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
1w02w13w24w313w014w015w116w217w319w420w521w622w723w824w928w329w430w531w640w141w742w848w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
24 touches
66 conflicts
0x00000000…0001
0xc1ff9f…b0fc
20 touches
45 conflicts
0x772ab420…c2f6
0x34b655…2a6f
12 touches
15 conflicts
0xc9dce17a…a1a1
0x34b655…2a6f
10 touches
10 conflicts
0x64aaadbf…f9f3
0x34b655…2a6f
8 touches
6 conflicts
0xfd42a6b9…4c81
0x34b655…2a6f
8 touches
6 conflicts
0x7e80bc27…c362
0xd32edf…ff58
7 touches
6 conflicts
0x1b930a2d…9ea5
0x34b655…2a6f
6 touches
3 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
66 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity