← previous blocknext block →recent activity

Analyzing

Block #87,621,742

20 transactions · 20 stateful · 2026-07-14 03:45:51 UTC

Parallelism

70/100

Blocked

35%

Avg conflicts / tx

1.05

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #87,621,742  ·  20 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

10 touches
10 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

10 touches
10 conflicts

0xac61d3a4…7da8

0x34b655…2a6f

8 touches
6 conflicts

0x68b75835…d6f3

0x34b655…2a6f

6 touches
3 conflicts

0x5170a218…3a84

0xc8689a…ee79

6 touches
3 conflicts

0x18e900fa…07f4

0x34b655…2a6f

6 touches
3 conflicts

0x25329a48…4e00

0x34b655…2a6f

6 touches
3 conflicts

0xcef0e4b7…46bf

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

10 conflicts on slot 0x6fe7d366be…a578ff

← previous block·next block →recent activity