← previous blocknext block →recent activity
Analyzing
Block #87,699,439
53 transactions · 40 stateful · 2026-07-14 12:25:08 UTC
Parallelism
70/100
Blocked
68%
Avg conflicts / tx
1.94
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #87,699,439 · 53 txs across 16 waves · depth 16
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
wave w13
wave w14
wave w15
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w06w17w39w411w012w115w220w321w024w125w026w127w228w329w431w532w633w740w443w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
18 touches
36 conflicts
0xb5a3b1be…8122
0x34b655…2a6f
12 touches
15 conflicts
0xac2a0273…721b
0x34b655…2a6f
12 touches
15 conflicts
0xf81d0d0f…cf78
0x34b655…2a6f
12 touches
15 conflicts
0x4f4085df…cf81
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0002
0x04fdea…47d7
8 touches
6 conflicts
0x3413a430…234a
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
36 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity