← previous blocknext block →recent activity
Analyzing
Block #87,699,353
19 transactions · 18 stateful · 2026-07-14 12:24:33 UTC
Parallelism
68/100
Blocked
44%
Avg conflicts / tx
1.05
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,699,353 · 19 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
3w04w15w26w38w411w512w013w114w215w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0006
0x0a2fbf…29b1
8 touches
6 conflicts
0x72ffca16…8abb
0x0a2fbf…29b1
8 touches
6 conflicts
0x72ffca16…8abc
0x0a2fbf…29b1
8 touches
6 conflicts
0xd5858ece…2d97
0x0a2fbf…29b1
8 touches
6 conflicts
0xd5858ece…2d98
0x0a2fbf…29b1
8 touches
6 conflicts
0xd5858ece…2d9b
0x0a2fbf…29b1
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0x17b720f5…ad7a
0x34b655…2a6f
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