← previous blocknext block →recent activity
Analyzing
Block #87,419,223
34 transactions · 28 stateful · 2026-07-13 05:10:46 UTC
Parallelism
62/100
Blocked
61%
Avg conflicts / tx
2.29
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #87,419,223 · 34 txs across 13 waves · depth 13
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
wave w12
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w07w18w19w210w311w412w513w614w716w817w920w1029w930w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
16 touches
28 conflicts
0x11d629eb…bcd9
0x34b655…2a6f
14 touches
21 conflicts
0x587911c7…9e01
0x34b655…2a6f
10 touches
10 conflicts
0xc6ed530e…fa7d
0x34b655…2a6f
10 touches
10 conflicts
0xc6fabe47…654e
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0xf3fbc9b8…ab58
0x34b655…2a6f
8 touches
6 conflicts
0x95c47f03…f1bb
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
28 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity