← previous blocknext block →recent activity
Analyzing
Block #87,417,006
21 transactions · 19 stateful · 2026-07-13 04:55:57 UTC
Parallelism
62/100
Blocked
58%
Avg conflicts / tx
1.76
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #87,417,006 · 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
3w04w15w26w37w48w59w610w720w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5b353877…605d
0x34b655…2a6f
14 touches
21 conflicts
0xfaef08b1…0696
0x34b655…2a6f
12 touches
15 conflicts
0xf2112d98…bb04
0x34b655…2a6f
12 touches
15 conflicts
0x63c900f4…2600
0x34b655…2a6f
12 touches
15 conflicts
0x922c7ebd…6600
0xc8689a…ee79
10 touches
10 conflicts
0x1eb9efa2…0c05
0x34b655…2a6f
10 touches
10 conflicts
0x3483ab79…8ed3
0x34b655…2a6f
10 touches
10 conflicts
0x366c7d57…0ed1
0x34b655…2a6f
10 touches
10 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 0x5b353877fb…57605d
Audit this contract →
← previous block·next block →recent activity