← previous blocknext block →recent activity

Analyzing

Block #87,754,682

21 transactions · 20 stateful · 2026-07-14 18:35:05 UTC

Parallelism

67/100

Blocked

45%

Avg conflicts / tx

1.05

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #87,754,682  ·  21 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xf3d10975…0d07

0x34b655…2a6f

8 touches
6 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

8 touches
6 conflicts

0xc36fa358…24cb

0x34b655…2a6f

8 touches
6 conflicts

0x9001f549…089d

0x34b655…2a6f

8 touches
6 conflicts

0x9ae859db…2d84

0x34b655…2a6f

6 touches
3 conflicts

0x70d66bd9…0ffa

0x34b655…2a6f

6 touches
3 conflicts

0x5c8c5129…7d88

0x34b655…2a6f

6 touches
3 conflicts

0x893e54e2…2205

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

6 conflicts on slot 0xf3d10975b0…050d07

← previous block·next block →recent activity