← previous blocknext block →recent activity
Analyzing
Block #87,706,480
24 transactions · 23 stateful · 2026-07-14 13:12:28 UTC
Parallelism
58/100
Blocked
61%
Avg conflicts / tx
2.17
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #87,706,480 · 24 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w26w37w48w59w610w711w812w917w219w121w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
20 touches
45 conflicts
0x5b145de0…367c
0xc8689a…ee79
16 touches
28 conflicts
0xeeaba9d3…b491
0x34b655…2a6f
16 touches
28 conflicts
0xa6389d47…9a28
0x34b655…2a6f
16 touches
28 conflicts
0x7837c02d…0965
0x34b655…2a6f
16 touches
28 conflicts
0x4560e5a8…b741
0x34b655…2a6f
16 touches
28 conflicts
0x67905f6e…02a1
0x34b655…2a6f
16 touches
28 conflicts
0x7f925d18…0689
0x34b655…2a6f
14 touches
21 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
45 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity