← previous blocknext block →recent activity

Analyzing

Block #87,751,326

18 transactions · 16 stateful · 2026-07-14 18:12:39 UTC

Parallelism

72/100

Blocked

56%

Avg conflicts / tx

1.44

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #87,751,326  ·  18 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x6f46250b…3bf2

0x34b655…2a6f

8 touches
6 conflicts

0xea4b86ec…900f

0x34b655…2a6f

8 touches
6 conflicts

0xcb76b2ed…89a5

0x34b655…2a6f

8 touches
6 conflicts

0x0733be30…112f

0x34b655…2a6f

8 touches
6 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

8 touches
6 conflicts

0xf3d10975…0d07

0x34b655…2a6f

6 touches
3 conflicts

0x29deea98…7b5e

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

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

6 conflicts on slot 0x6f46250b20…823bf2

← previous block·next block →recent activity