← previous blocknext block →recent activity
Analyzing
Block #87,626,611
21 transactions · 19 stateful · 2026-07-14 04:18:26 UTC
Parallelism
62/100
Blocked
58%
Avg conflicts / tx
1.9
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #87,626,611 · 21 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w37w48w59w210w313w614w719w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
14 touches
21 conflicts
0xe197e523…ef9c
0x34b655…2a6f
12 touches
15 conflicts
0xf2f4727d…cdb7
0x34b655…2a6f
10 touches
10 conflicts
0x9040c7dc…eac5
0x34b655…2a6f
8 touches
6 conflicts
0x4c188934…158e
0x34b655…2a6f
8 touches
6 conflicts
0x49f75237…44f4
0x34b655…2a6f
6 touches
3 conflicts
0x6f761690…95bd
0x34b655…2a6f
6 touches
3 conflicts
0x9599eb41…b5d6
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
21 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity