← previous blocknext block →recent activity
Analyzing
Block #87,497,034
17 transactions · 14 stateful · 2026-07-13 13:51:02 UTC
Parallelism
76/100
Blocked
43%
Avg conflicts / tx
0.59
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,497,034 · 17 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
4w06w17w28w311w013w114w216w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa37d59c6…996b
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0xb670a63e…ead8
0x34b655…2a6f
8 touches
6 conflicts
0x366c7d57…0ed1
0x34b655…2a6f
6 touches
3 conflicts
0x46eecd1f…955f
0x34b655…2a6f
6 touches
3 conflicts
0x51cd1d5b…24ed
0x34b655…2a6f
6 touches
3 conflicts
0x5d99e0ac…1d08
0x34b655…2a6f
6 touches
3 conflicts
0x63c900f4…2600
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 0xa37d59c66f…3f996b
Audit this contract →
← previous block·next block →recent activity