← previous blocknext block →recent activity

Analyzing

Block #87,704,029

26 transactions · 17 stateful · 2026-07-14 12:56:03 UTC

Parallelism

81/100

Blocked

41%

Avg conflicts / tx

0.38

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #87,704,029  ·  26 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x92385428…6941

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x05975727…7fcf

0x34b655…2a6f

4 touches
1 conflict

0x0c15f714…46ab

0x34b655…2a6f

4 touches
1 conflict

0x0f556856…2916

0x34b655…2a6f

4 touches
1 conflict

0x3f93d576…f1de

0x34b655…2a6f

4 touches
1 conflict

0x40a9339c…6572

0x34b655…2a6f

4 touches
1 conflict

0x7ae94b74…7aef

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 0x92385428ad…dc6941

← previous block·next block →recent activity