← previous blocknext block →recent activity
Analyzing
Block #87,880,057
18 transactions · 18 stateful · 2026-07-15 08:33:42 UTC
Parallelism
67/100
Blocked
50%
Avg conflicts / tx
1.39
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,880,057 · 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
2w04w15w26w37w48w510w011w112w213w314w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0006
0x0a2fbf…29b1
10 touches
10 conflicts
0x25c40209…fee6
0x0a2fbf…29b1
10 touches
10 conflicts
0x25c40209…fee7
0x0a2fbf…29b1
10 touches
10 conflicts
0x68cdfd61…4142
0x0a2fbf…29b1
10 touches
10 conflicts
0x68cdfd61…4143
0x0a2fbf…29b1
10 touches
10 conflicts
0x68cdfd61…4146
0x0a2fbf…29b1
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0005
0x370e2e…63b4
10 touches
10 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: 0x0a2fbf2d…f729b1
10 conflicts on slot 0x0000000000…000006
Audit this contract →
← previous block·next block →recent activity