← previous blocknext block →recent activity

Analyzing

Block #87,594,006

22 transactions · 20 stateful · 2026-07-14 00:40:24 UTC

Parallelism

68/100

Blocked

50%

Avg conflicts / tx

1.05

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #87,594,006  ·  22 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

0xd93edb3f…94ec

0x34b655…2a6f

10 touches
10 conflicts

0xe5bb3628…e5f1

0x34b655…2a6f

8 touches
6 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

8 touches
6 conflicts

0x3ca9a061…1f41

0x34b655…2a6f

6 touches
3 conflicts

0x45a2ce5b…1492

0x34b655…2a6f

6 touches
3 conflicts

0x53bddbe8…2e5e

0x34b655…2a6f

6 touches
3 conflicts

0x63f8a50d…333b

0x34b655…2a6f

6 touches
3 conflicts

0x077d58c3…8ed7

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 0xd93edb3f20…0394ec

← previous block·next block →recent activity