← previous blocknext block →recent activity

Analyzing

Block #87,593,047

22 transactions · 21 stateful · 2026-07-14 00:33:59 UTC

Parallelism

64/100

Blocked

48%

Avg conflicts / tx

1.36

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #87,593,047  ·  22 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

0xa6b89ebb…a66e

0x34b655…2a6f

12 touches
15 conflicts

0xe5bb3628…e5f1

0x34b655…2a6f

8 touches
6 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

8 touches
6 conflicts

0x53bddbe8…2e5e

0x34b655…2a6f

6 touches
3 conflicts

0x6c0d4c60…31c4

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x875164c2…f8a2

0x34b655…2a6f

6 touches
3 conflicts

0x92385428…6941

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

15 conflicts on slot 0xa6b89ebbaf…5fa66e

← previous block·next block →recent activity