← previous blocknext block →recent activity
Analyzing
Block #87,357,563
20 transactions · 19 stateful · 2026-07-12 22:18:17 UTC
Parallelism
70/100
Blocked
42%
Avg conflicts / tx
1.1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,357,563 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w07w18w29w311w012w413w414w517w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
12 touches
15 conflicts
0x7506443a…4820
0x34b655…2a6f
8 touches
6 conflicts
0x922c7ebd…6600
0xc8689a…ee79
8 touches
6 conflicts
0x3483ab79…8ed3
0x34b655…2a6f
8 touches
6 conflicts
0xdbc62196…3245
0x34b655…2a6f
8 touches
6 conflicts
0xd3ef5630…0de9
0x34b655…2a6f
8 touches
6 conflicts
0xc368d7fd…aaec
0x34b655…2a6f
8 touches
6 conflicts
0xc2dda872…7e3e
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
15 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity