← previous blocknext block →recent activity

Analyzing

Block #87,690,193

14 transactions · 13 stateful · 2026-07-14 11:23:19 UTC

Parallelism

86/100

Blocked

31%

Avg conflicts / tx

0.29

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #87,690,193  ·  14 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

0x4e135144…4167

0x34b655…2a6f

4 touches
1 conflict

0x624a8689…c9a9

0x34b655…2a6f

4 touches
1 conflict

0x6363986b…fe3a

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4aa

0x34b655…2a6f

4 touches
1 conflict

0x80d2f96b…d068

0x34b655…2a6f

4 touches
1 conflict

0xe5a9274d…78d7

0x34b655…2a6f

4 touches
1 conflict

0xe5bb3628…e5f1

0x34b655…2a6f

4 touches
1 conflict

0x889d5e90…929a

0x2a68ba…90c5

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 0x4e135144ab…684167

← previous block·next block →recent activity