← previous blocknext block →recent activity
Analyzing
Block #87,716,425
51 transactions · 44 stateful · 2026-07-14 14:19:08 UTC
Parallelism
67/100
Blocked
70%
Avg conflicts / tx
2.63
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #87,716,425 · 51 txs across 17 waves · depth 17
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
wave w16
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w27w38w49w010w111w212w013w124w125w230w731w832w936w1037w1139w341w242w443w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
22 touches
55 conflicts
0xbf78ee7f…e7fd
0x34b655…2a6f
14 touches
21 conflicts
0x28ceceef…ecc2
0x34b655…2a6f
12 touches
15 conflicts
0x2bd2aeca…93b2
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…002d
0x1b6862…e19c
8 touches
6 conflicts
0xd4c913d7…343d
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x4a1e17cf…f6e3
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
55 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity