← previous blocknext block →recent activity

Analyzing

Block #87,785,747

22 transactions · 20 stateful · 2026-07-14 22:02:55 UTC

Parallelism

59/100

Blocked

45%

Avg conflicts / tx

1.32

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #87,785,747  ·  22 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

10 touches
10 conflicts

0x0dd44476…ef40

0x34b655…2a6f

8 touches
6 conflicts

0x9001f549…089d

0x34b655…2a6f

8 touches
6 conflicts

0x68761f35…6026

0x34b655…2a6f

6 touches
3 conflicts

0xfb0022d6…1264

0x34b655…2a6f

6 touches
3 conflicts

0x28c62bca…b746

0x34b655…2a6f

6 touches
3 conflicts

0x55c2c22c…0474

0x34b655…2a6f

6 touches
3 conflicts

0xb9801357…5fef

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

10 conflicts on slot 0x6fe7d366be…a578ff

← previous block·next block →recent activity