← previous blocknext block →recent activity
Analyzing
Block #87,711,406
21 transactions · 19 stateful · 2026-07-14 13:45:26 UTC
Parallelism
86/100
Blocked
53%
Avg conflicts / tx
0.62
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,711,406 · 21 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w06w17w210w111w212w013w015w116w217w118w220w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xebbeecfd…c00b
0x0a2fbf…29b1
6 touches
3 conflicts
0x00000000…0005
0x370e2e…63b4
6 touches
3 conflicts
0xebbeecfd…c00c
0x0a2fbf…29b1
6 touches
3 conflicts
0x8616266b…0258
0x0a2fbf…29b1
6 touches
3 conflicts
0x0dd44476…ef40
0x34b655…2a6f
6 touches
3 conflicts
0x8616266b…0259
0x0a2fbf…29b1
6 touches
3 conflicts
0x1bff683e…7ecb
0x754704…b603
6 touches
3 conflicts
0x55b4e430…44cb
0x754704…b603
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: 0x0a2fbf2d…f729b1
3 conflicts on slot 0xebbeecfd48…b5c00b
Audit this contract →
← previous block·next block →recent activity