← previous blocknext block →recent activity
Analyzing
Block #87,662,016
44 transactions · 36 stateful · 2026-07-14 08:15:01 UTC
Parallelism
64/100
Blocked
72%
Avg conflicts / tx
2.39
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #87,662,016 · 44 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
1w02w13w24w35w06w17w08w09w114w115w216w317w418w519w620w721w831w233w1335w336w440w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
24 touches
66 conflicts
0x745952b2…d90c
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…003d
0x40c49f…2af0
8 touches
6 conflicts
0x7d3c50c5…2279
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xffa7d0a4…b10a
0x40c49f…2af0
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0xaeb05e7d…aa19
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