← previous blocknext block →recent activity

Analyzing

Block #87,705,960

21 transactions · 19 stateful · 2026-07-14 13:09:00 UTC

Parallelism

76/100

Blocked

42%

Avg conflicts / tx

0.52

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #87,705,960  ·  21 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

6 touches
3 conflicts

0x889d5e90…929a

0x2a68ba…90c5

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x1d9a7c5e…bf92

0x34b655…2a6f

4 touches
1 conflict

0x2754c3f9…9863

0x34b655…2a6f

4 touches
1 conflict

0x37904164…3406

0x34b655…2a6f

4 touches
1 conflict

0xa57576bb…e01f

0x34b655…2a6f

4 touches
1 conflict

0xad09dd03…27d0

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

← previous block·next block →recent activity