← previous blocknext block →recent activity

Analyzing

Block #87,589,716

32 transactions · 25 stateful · 2026-07-14 00:11:42 UTC

Parallelism

75/100

Blocked

48%

Avg conflicts / tx

0.94

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #87,589,716  ·  32 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

0xd93edb3f…94ec

0x34b655…2a6f

8 touches
6 conflicts

0x21c9fd73…dae4

0x34b655…2a6f

6 touches
3 conflicts

0x34d95d94…3a16

0x34b655…2a6f

6 touches
3 conflicts

0x67905f6e…02a1

0x34b655…2a6f

6 touches
3 conflicts

0x875164c2…f8a2

0x34b655…2a6f

6 touches
3 conflicts

0x9dc4d309…2302

0x34b655…2a6f

6 touches
3 conflicts

0x9fd37234…2731

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

21 conflicts on slot 0x6fe7d366be…a578ff

← previous block·next block →recent activity