← previous blocknext block →recent activity
Analyzing
Block #87,121,677
20 transactions · 19 stateful · 2026-07-11 20:00:24 UTC
Parallelism
65/100
Blocked
53%
Avg conflicts / tx
1.4
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,121,677 · 20 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w06w47w08w19w210w313w414w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
12 touches
15 conflicts
0x9fb27666…4250
0xd32edf…ff58
9 touches
10 conflicts
0x2aad2854…698e
0x34b655…2a6f
8 touches
6 conflicts
0x2dedf9be…404e
0x34b655…2a6f
8 touches
6 conflicts
0x321eac33…6aca
0x34b655…2a6f
8 touches
6 conflicts
0x398b64f7…4b55
0x34b655…2a6f
8 touches
6 conflicts
0x727fbce7…0c80
0x34b655…2a6f
8 touches
6 conflicts
0x7ae63663…9d94
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 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity