← previous blocknext block →recent activity
Analyzing
Block #87,729,618
40 transactions · 37 stateful · 2026-07-14 15:47:26 UTC
Parallelism
68/100
Blocked
59%
Avg conflicts / tx
1.7
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #87,729,618 · 40 txs across 13 waves · depth 13
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w06w17w08w112w013w214w315w416w517w618w726w435w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
14 touches
21 conflicts
0xa55c4598…2988
0x34b655…2a6f
14 touches
21 conflicts
0x67905f6e…02a1
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0002
0x04fdea…47d7
8 touches
6 conflicts
0x312e4698…54c0
0x34b655…2a6f
8 touches
6 conflicts
0x4ca1448c…9de6
0x34b655…2a6f
8 touches
6 conflicts
0x521553ff…d548
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
21 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity