← previous blocknext block →recent activity
Analyzing
Block #87,729,691
21 transactions · 19 stateful · 2026-07-14 15:47:55 UTC
Parallelism
81/100
Blocked
37%
Avg conflicts / tx
0.48
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,729,691 · 21 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w19w210w311w114w119w120w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x8ff85b19…dde0
0x34b655…2a6f
4 touches
1 conflict
0x033dddd2…ac15
0x34b655…2a6f
4 touches
1 conflict
0xc4de6652…13f4
0x34b655…2a6f
4 touches
1 conflict
0xc7981744…932f
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x521553ff…d548
0x34b655…2a6f
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
6 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity