← previous blocknext block →recent activity

Analyzing

Block #87,253,048

29 transactions · 28 stateful · 2026-07-12 10:39:27 UTC

Parallelism

76/100

Blocked

61%

Avg conflicts / tx

1.69

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #87,253,048  ·  29 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

0xfaef08b1…0696

0x34b655…2a6f

12 touches
15 conflicts

0xf192a0f9…2e6d

0xd32edf…ff58

11 touches
15 conflicts

0x8cc1393f…07fb

0x34b655…2a6f

10 touches
10 conflicts

0xe2307994…acad

0x34b655…2a6f

10 touches
10 conflicts

0x00000000…001b

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…002b

0x1b6862…e19c

8 touches
6 conflicts

0xba5743c7…21c2

0x1b6862…e19c

8 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

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: Perpl

15 conflicts on slot 0xfaef08b108…f90696

← previous block·next block →recent activity