← previous blocknext block →recent activity

Analyzing

Block #87,735,816

26 transactions · 21 stateful · 2026-07-14 16:28:53 UTC

Parallelism

88/100

Blocked

29%

Avg conflicts / tx

0.38

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #87,735,816  ·  26 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

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0x3e0dc4b4…8392

0x34b655…2a6f

6 touches
3 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

6 touches
3 conflicts

0x307414a5…7214

0x34b655…2a6f

6 touches
3 conflicts

0x4bb0bfb0…8f11

0x34b655…2a6f

4 touches
1 conflict

0x6fe7d366…78ff

0x34b655…2a6f

4 touches
1 conflict

0x7aad02c6…b979

0x34b655…2a6f

4 touches
1 conflict

0x80ce19e2…37d3

0x34b655…2a6f

4 touches
1 conflict

0x83e779c0…b0c2

0x34b655…2a6f

4 touches
1 conflict

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

3 conflicts on slot 0x3e0dc4b4b3…398392

← previous block·next block →recent activity