← previous blocknext block →recent activity
Analyzing
Block #87,626,767
22 transactions · 21 stateful · 2026-07-14 04:19:28 UTC
Parallelism
68/100
Blocked
57%
Avg conflicts / tx
1.64
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,626,767 · 22 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
2w04w15w26w37w48w59w620w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
14 touches
21 conflicts
0xf2f4727d…cdb7
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x5b145de0…367c
0xc8689a…ee79
8 touches
6 conflicts
0x49f75237…44f4
0x34b655…2a6f
8 touches
6 conflicts
0x7d7ff6bb…f729
0x34b655…2a6f
8 touches
6 conflicts
0x8d4a873e…1ada
0x34b655…2a6f
8 touches
6 conflicts
0x9599eb41…b5d6
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