← previous blocknext block →recent activity

Analyzing

Block #87,578,416

20 transactions · 16 stateful · 2026-07-13 22:56:08 UTC

Parallelism

80/100

Blocked

38%

Avg conflicts / tx

0.55

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #87,578,416  ·  20 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

0x0733be30…112f

0x34b655…2a6f

4 touches
1 conflict

0x0ea46b1d…c9a4

0x34b655…2a6f

4 touches
1 conflict

0x2ce92217…a204

0x34b655…2a6f

4 touches
1 conflict

0x40a9339c…6571

0x34b655…2a6f

4 touches
1 conflict

0x40a9339c…6572

0x34b655…2a6f

4 touches
1 conflict

0x4d73f502…968b

0x34b655…2a6f

4 touches
1 conflict

0x5d46d59a…e176

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