← previous blocknext block →recent activity

Analyzing

Block #87,585,516

21 transactions · 18 stateful · 2026-07-13 23:43:37 UTC

Parallelism

57/100

Blocked

61%

Avg conflicts / tx

1.43

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #87,585,516  ·  21 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0xd2453506…54e4

0x34b655…2a6f

12 touches
15 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

8 touches
6 conflicts

0xad0c7701…1d83

0x34b655…2a6f

8 touches
6 conflicts

0xde4c010f…59ad

0x34b655…2a6f

8 touches
6 conflicts

0x3a61096b…5107

0x34b655…2a6f

8 touches
6 conflicts

0x3c8c4674…a567

0x34b655…2a6f

6 touches
3 conflicts

0x4d9858eb…7098

0x34b655…2a6f

6 touches
3 conflicts

0x63c900f4…2600

0x34b655…2a6f

6 touches
3 conflicts

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

15 conflicts on slot 0xd2453506e1…f954e4

← previous block·next block →recent activity