← previous blocknext block →recent activity

Analyzing

Block #87,620,476

22 transactions · 19 stateful · 2026-07-14 03:37:23 UTC

Parallelism

77/100

Blocked

42%

Avg conflicts / tx

0.68

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #87,620,476  ·  22 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

0x6fe7d366…78ff

0x34b655…2a6f

8 touches
6 conflicts

0x745952b2…d90c

0x34b655…2a6f

8 touches
6 conflicts

0x7cd78950…607c

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0001

0xc1ff9f…b0fc

4 touches
1 conflict

0xb268a300…5f0c

0x34b655…2a6f

4 touches
1 conflict

0xe6bc2816…1787

0x34b655…2a6f

4 touches
1 conflict

0xfa61cca5…41ee

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x851145…3f07

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 0x6fe7d366be…a578ff

← previous block·next block →recent activity