← previous blocknext block →recent activity
Analyzing
Block #87,717,642
49 transactions · 39 stateful · 2026-07-14 14:27:19 UTC
Parallelism
75/100
Blocked
69%
Avg conflicts / tx
1.61
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #87,717,642 · 49 txs across 12 waves · depth 12
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w18w09w113w014w116w217w318w019w120w221w322w423w524w625w726w828w129w232w134w736w237w240w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
18 touches
36 conflicts
0x6a1604d1…3e8a
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0001
0xc1ff9f…b0fc
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x67905f6e…02a1
0x34b655…2a6f
6 touches
3 conflicts
0x7525206c…fbd5
0x34b655…2a6f
6 touches
3 conflicts
0xaf5570f4…e727
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
36 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity