← previous blocknext block →recent activity

Analyzing

Block #87,710,507

26 transactions · 23 stateful · 2026-07-14 13:39:25 UTC

Parallelism

69/100

Blocked

61%

Avg conflicts / tx

1.46

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #87,710,507  ·  26 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x64aaadbf…f9f3

0x34b655…2a6f

8 touches
6 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0xf5ea108a…dbf6

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0xa6afd3…d132

6 touches
3 conflicts

0x3464bbc5…a323

0xa6afd3…d132

6 touches
3 conflicts

0x889d5e90…929a

0x2a68ba…90c5

6 touches
3 conflicts

0xf219f7cf…7379

0xa6afd3…d132

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