← previous blocknext block →recent activity
Analyzing
Block #87,712,734
20 transactions · 16 stateful · 2026-07-14 13:54:19 UTC
Parallelism
65/100
Blocked
44%
Avg conflicts / tx
1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,712,734 · 20 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w37w48w512w618w019w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbf78ee7f…e7fd
0x34b655…2a6f
10 touches
10 conflicts
0xb2a25bac…c741
0x34b655…2a6f
10 touches
10 conflicts
0x820b2f6b…9263
0x34b655…2a6f
10 touches
10 conflicts
0x1716b13d…99cc
0xc8689a…ee79
8 touches
6 conflicts
0x52e57273…fe8f
0x34b655…2a6f
8 touches
6 conflicts
0x563ae507…382e
0x34b655…2a6f
8 touches
6 conflicts
0x64800813…db9f
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
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
10 conflicts on slot 0xbf78ee7fb5…b5e7fd
Audit this contract →
← previous block·next block →recent activity