← previous blocknext block →recent activity

Analyzing

Block #87,419,305

25 transactions · 24 stateful · 2026-07-13 05:11:19 UTC

Parallelism

64/100

Blocked

50%

Avg conflicts / tx

1.4

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #87,419,305  ·  25 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0x0733be30…112f

0x34b655…2a6f

8 touches
6 conflicts

0x6e27bdfb…108a

0x34b655…2a6f

8 touches
6 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

8 touches
6 conflicts

0x95c47f03…f1bb

0x34b655…2a6f

8 touches
6 conflicts

0xd330c0c5…6f64

0x34b655…2a6f

8 touches
6 conflicts

0x8a35acfb…d1ad

0xb1dbf0…c0d3

8 touches
6 conflicts

0x8a35acfb…d1ae

0xb1dbf0…c0d3

8 touches
6 conflicts

0x5ba51e87…44ee

0xb1dbf0…c0d3

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 0x0733be30d6…38112f

← previous block·next block →recent activity