← previous blocknext block →recent activity

Analyzing

Block #87,705,710

26 transactions · 24 stateful · 2026-07-14 13:07:19 UTC

Parallelism

73/100

Blocked

38%

Avg conflicts / tx

1

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #87,705,710  ·  26 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others

Conflict graph

Blocked by

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0x6fe7d366…78ff

0x34b655…2a6f

14 touches
21 conflicts

0x5b145de0…367c

0xc8689a…ee79

6 touches
3 conflicts

0x8fa9bc45…e08f

0xa6afd3…d132

6 touches
3 conflicts

0x43fab434…896f

0xa6afd3…d132

6 touches
3 conflicts

0x00000000…003d

0xa6afd3…d132

6 touches
3 conflicts

0xeeaba9d3…b491

0x34b655…2a6f

6 touches
3 conflicts

0x8fe37a3f…4c89

0x34b655…2a6f

6 touches
3 conflicts

0x7837c02d…0965

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

21 conflicts on slot 0x6fe7d366be…a578ff

← previous block·next block →recent activity