← previous blocknext block →recent activity

Analyzing

Block #87,621,982

20 transactions · 17 stateful · 2026-07-14 03:47:27 UTC

Parallelism

70/100

Blocked

47%

Avg conflicts / tx

0.9

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #87,621,982  ·  20 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x34d95d94…3a16

0x34b655…2a6f

10 touches
10 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

10 touches
10 conflicts

0x28c62bca…b746

0x34b655…2a6f

8 touches
6 conflicts

0xd19c9d38…b459

0x34b655…2a6f

8 touches
6 conflicts

0xf2f4727d…cdb7

0x34b655…2a6f

8 touches
6 conflicts

0x49f75237…44f4

0x34b655…2a6f

8 touches
6 conflicts

0x5b145de0…367c

0xc8689a…ee79

8 touches
6 conflicts

0x875164c2…f8a2

0x34b655…2a6f

8 touches
6 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 0x34d95d945c…603a16

← previous block·next block →recent activity