← previous blocknext block →recent activity

Analyzing

Block #87,920,806

28 transactions · 19 stateful · 2026-07-15 13:06:15 UTC

Parallelism

82/100

Blocked

42%

Avg conflicts / tx

0.54

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #87,920,806  ·  28 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

0xc788862c…c259

0x34b655…2a6f

8 touches
6 conflicts

0x405da62e…192a

0xa6afd3…d132

8 touches
6 conflicts

0x00000000…003d

0xa6afd3…d132

6 touches
3 conflicts

0x731f2745…9370

0xa6afd3…d132

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0xb8fccd1b…b5f2

0x2b46c0…1669

4 touches
1 conflict

0x00000000…00c9

0x34b655…2a6f

4 touches
1 conflict

0x1ec7ada6…505b

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

6 conflicts on slot 0xc788862c2e…6ec259

← previous block·next block →recent activity