← previous blocknext block →recent activity

Analyzing

Block #89,415,010

16 transactions · 16 stateful · 2026-07-22 11:40:22 UTC

Parallelism

69/100

Blocked

50%

Avg conflicts / tx

1.06

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #89,415,010  ·  16 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

0xbcbf5d09…8bac

0x34b655…2a6f

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x3e3f27ce…580c

0x34b655…2a6f

4 touches
1 conflict

0x748ce49f…a12c

0x34b655…2a6f

4 touches
1 conflict

0x810a3aa2…0227

0x34b655…2a6f

4 touches
1 conflict

0x8ad18e06…472a

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

10 conflicts on slot 0xbcbf5d09a8…c68bac

← previous block·next block →recent activity