← previous blocknext block →recent activity
Analyzing
Block #87,506,469
14 transactions · 12 stateful · 2026-07-13 14:54:12 UTC
Parallelism
64/100
Blocked
50%
Avg conflicts / tx
0.71
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,506,469 · 14 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w27w08w19w210w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x0ba865dd…a249
0x34b655…2a6f
6 touches
3 conflicts
0x2f702750…347d
0x34b655…2a6f
6 touches
3 conflicts
0x41320d8e…f9fb
0x34b655…2a6f
6 touches
3 conflicts
0x4f99c86b…25a7
0x34b655…2a6f
6 touches
3 conflicts
0x58aa2cb3…5758
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
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
6 conflicts on slot 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity