← previous blocknext block →recent activity
Analyzing
Block #87,729,647
21 transactions · 20 stateful · 2026-07-14 15:47:37 UTC
Parallelism
71/100
Blocked
40%
Avg conflicts / tx
0.86
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,729,647 · 21 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
2w03w14w05w06w17w19w210w311w414w519w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x521553ff…d548
0x34b655…2a6f
12 touches
15 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x92385428…6941
0x34b655…2a6f
10 touches
10 conflicts
0xa3c36de0…3cf3
0x34b655…2a6f
8 touches
6 conflicts
0x64aaadbf…f9f3
0x34b655…2a6f
8 touches
6 conflicts
0x7c7eff13…16db
0x34b655…2a6f
6 touches
3 conflicts
0x5bb46f6c…7693
0x34b655…2a6f
6 touches
3 conflicts
0xfcb6731c…b151
0x34b655…2a6f
6 touches
3 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 0x521553ff41…c5d548
Audit this contract →
← previous block·next block →recent activity