← previous blocknext block →recent activity
Analyzing
Block #87,699,004
28 transactions · 26 stateful · 2026-07-14 12:22:13 UTC
Parallelism
79/100
Blocked
50%
Avg conflicts / tx
0.71
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,699,004 · 28 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
1w02w13w25w07w08w19w112w015w316w218w119w220w221w325w326w427w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x86b36626…cd70
0x34b655…2a6f
6 touches
3 conflicts
0x86b36626…cd71
0x34b655…2a6f
6 touches
3 conflicts
0xafc8de01…40dc
0x34b655…2a6f
6 touches
3 conflicts
0xd6b45088…3627
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
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
3 conflicts on slot 0x86b36626ea…68cd70
Audit this contract →
← previous block·next block →recent activity