← previous blocknext block →recent activity

Analyzing

Block #87,752,825

27 transactions · 20 stateful · 2026-07-14 18:22:40 UTC

Parallelism

85/100

Blocked

35%

Avg conflicts / tx

0.52

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #87,752,825  ·  27 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xb9a0c34e…003f

0xd32edf…ff58

7 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0x2eca27fa…dba4

0x34b655…2a6f

4 touches
1 conflict

0xf5a81f8f…a065

0x34b655…2a6f

4 touches
1 conflict

0xfed09e59…a493

0x34b655…2a6f

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0xec2a8d79…70cb

0x34b655…2a6f

4 touches
1 conflict

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

6 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity