← previous blocknext block →recent activity

Analyzing

Block #87,919,079

24 transactions · 17 stateful · 2026-07-15 12:54:42 UTC

Parallelism

79/100

Blocked

35%

Avg conflicts / tx

0.63

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #87,919,079  ·  24 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

0xc948dbdc…199a

0x34b655…2a6f

8 touches
6 conflicts

0xaba2bbbd…f44a

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0xf3d10975…0d07

0x34b655…2a6f

6 touches
3 conflicts

0xc6e33caa…ec53

0x34b655…2a6f

6 touches
3 conflicts

0x8ca57c5a…9cfd

0x34b655…2a6f

4 touches
1 conflict

0x9aea124d…de52

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

← previous block·next block →recent activity