← previous blocknext block →recent activity

Analyzing

Block #87,643,907

16 transactions · 14 stateful · 2026-07-14 06:14:02 UTC

Parallelism

88/100

Blocked

14%

Avg conflicts / tx

0.13

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #87,643,907  ·  16 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x7e5ea60a…c4ab

0x34b655…2a6f

4 touches
1 conflict

0x85c84f98…06d7

0x34b655…2a6f

4 touches
1 conflict

0x0a6a5b44…d0e5

0x34b655…2a6f

4 touches
1 conflict

0x92385428…6941

0x34b655…2a6f

4 touches
1 conflict

0x96efe05d…5d48

0x34b655…2a6f

4 touches
1 conflict

0xc3a8e1d6…e816

0x34b655…2a6f

4 touches
1 conflict

0x3f25409b…f92b

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

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

1 conflict on slot 0x7e5ea60ab2…b0c4ab

← previous block·next block →recent activity