← previous blocknext block →recent activity

Analyzing

Block #87,626,454

11 transactions · 10 stateful · 2026-07-14 04:17:23 UTC

Parallelism

73/100

Blocked

20%

Avg conflicts / tx

0.18

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #87,626,454  ·  11 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

0xbcbf5d09…8bac

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xc514314c…1aa4

0x34b655…2a6f

4 touches
1 conflict

0x889d5e90…929a

0x2a68ba…90c5

2 touches
0 conflicts

0x0893a322…b9e5

0x34b655…2a6f

2 touches
0 conflicts

0x41ce581d…51be

0x34b655…2a6f

2 touches
0 conflicts

0x62030a81…91be

0x34b655…2a6f

2 touches
0 conflicts

0x62d2152c…c65a

0x34b655…2a6f

2 touches
0 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

1 conflict on slot 0xbcbf5d09a8…c68bac

← previous block·next block →recent activity