← previous blocknext block →recent activity

Analyzing

Block #87,626,363

20 transactions · 18 stateful · 2026-07-14 04:16:46 UTC

Parallelism

80/100

Blocked

39%

Avg conflicts / tx

0.6

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #87,626,363  ·  20 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x737acb78…fce8

0x34b655…2a6f

6 touches
3 conflicts

0xf06ab8d8…3589

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0001

0xc1ff9f…b0fc

6 touches
3 conflicts

0x46d6bfe6…5b21

0x34b655…2a6f

4 touches
1 conflict

0x5b6a7552…a4b8

0x34b655…2a6f

4 touches
1 conflict

0x5b6a7552…a4b9

0x34b655…2a6f

4 touches
1 conflict

0x62cc9214…441b

0x34b655…2a6f

4 touches
1 conflict

0x6fe7d366…78ff

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 0x737acb7813…fafce8

← previous block·next block →recent activity