← previous blocknext block →recent activity
Analyzing
Block #87,497,007
18 transactions · 17 stateful · 2026-07-13 13:50:51 UTC
Parallelism
67/100
Blocked
53%
Avg conflicts / tx
0.94
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,497,007 · 18 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
1w02w03w14w25w36w47w210w311w412w117w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x32dfa6a9…12f6
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x366c7d57…0ed1
0x34b655…2a6f
6 touches
3 conflicts
0x42f1a6e5…03a6
0x34b655…2a6f
6 touches
3 conflicts
0x4674c52e…4901
0x34b655…2a6f
6 touches
3 conflicts
0x46eecd1f…955f
0x34b655…2a6f
6 touches
3 conflicts
0x51cd1d5b…24ed
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity