← previous blocknext block →recent activity

Analyzing

Block #89,414,592

20 transactions · 18 stateful · 2026-07-22 11:37:34 UTC

Parallelism

50/100

Blocked

56%

Avg conflicts / tx

1.1

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #89,414,592  ·  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

0x1941b441…5889

0x34b655…2a6f

6 touches
3 conflicts

0x322dcd34…8718

0x34b655…2a6f

6 touches
3 conflicts

0x4681609f…6493

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xda27c764…7fab

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x63da8263…7a24

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

3 conflicts on slot 0x1941b4413e…0c5889

← previous block·next block →recent activity