← previous blocknext block →recent activity

Analyzing

Block #87,709,138

28 transactions · 25 stateful · 2026-07-14 13:30:15 UTC

Parallelism

89/100

Blocked

24%

Avg conflicts / tx

0.29

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #87,709,138  ·  28 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x0dd44476…ef40

0x34b655…2a6f

6 touches
3 conflicts

0x92385428…6941

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0002

0x04fdea…47d7

6 touches
3 conflicts

0xc2e36a04…b85e

0x851145…3f07

4 touches
1 conflict

0x191c9934…f4f4

0x34b655…2a6f

4 touches
1 conflict

0x64a058c6…74a1

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

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

3 conflicts on slot 0x0dd44476b8…7fef40

← previous block·next block →recent activity