← previous blocknext block →recent activity

Analyzing

Block #89,279,983

20 transactions · 17 stateful · 2026-07-21 20:37:47 UTC

Parallelism

50/100

Blocked

59%

Avg conflicts / tx

1.8

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #89,279,983  ·  20 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0xd98b3c10…67b8

0x34b655…2a6f

14 touches
21 conflicts

0xc9dce17a…a1a1

0x34b655…2a6f

12 touches
15 conflicts

0xd4b0bafb…80ac

0x34b655…2a6f

8 touches
6 conflicts

0x7525206c…fbd5

0x34b655…2a6f

8 touches
6 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

6 touches
3 conflicts

0x7aad02c6…b979

0x34b655…2a6f

6 touches
3 conflicts

0xe5bb3628…e5f1

0x34b655…2a6f

6 touches
3 conflicts

0xb5cddf91…0abf

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

21 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity