← previous blocknext block →recent activity
Analyzing
Block #87,713,030
24 transactions · 21 stateful · 2026-07-14 13:56:18 UTC
Parallelism
75/100
Blocked
48%
Avg conflicts / tx
1.17
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,713,030 · 24 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
1w02w13w25w06w07w18w29w311w012w113w215w416w322w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa6389d47…9a28
0x34b655…2a6f
12 touches
15 conflicts
0x5b145de0…367c
0xc8689a…ee79
8 touches
6 conflicts
0x53bddbe8…2e5e
0x34b655…2a6f
8 touches
6 conflicts
0x560ed681…07e6
0x34b655…2a6f
8 touches
6 conflicts
0x67905f6e…02a1
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xd11dcf4e…518f
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 0xa6389d470d…f19a28
Audit this contract →
← previous block·next block →recent activity