← previous blocknext block →recent activity
Analyzing
Block #87,670,687
15 transactions · 13 stateful · 2026-07-14 09:12:57 UTC
Parallelism
67/100
Blocked
46%
Avg conflicts / tx
0.8
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,670,687 · 15 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
5w06w07w18w29w310w111w212w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0006
0x0a2fbf…29b1
8 touches
6 conflicts
0x0dd079f2…5ac6
0x0a2fbf…29b1
8 touches
6 conflicts
0x0dd079f2…5ac7
0x0a2fbf…29b1
8 touches
6 conflicts
0x0dd079f2…5aca
0x0a2fbf…29b1
8 touches
6 conflicts
0x36390842…358f
0x0a2fbf…29b1
8 touches
6 conflicts
0x36390842…3590
0x0a2fbf…29b1
8 touches
6 conflicts
0x00000000…0005
0x370e2e…63b4
8 touches
6 conflicts
0x377b15b8…b4c3
0x370e2e…63b4
8 touches
6 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
6 conflicts on slot 0x0000000000…000006
Audit this contract →
← previous block·next block →recent activity