← previous blocknext block →recent activity

Analyzing

Block #89,415,070

21 transactions · 18 stateful · 2026-07-22 11:40:46 UTC

Parallelism

81/100

Blocked

39%

Avg conflicts / tx

0.62

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #89,415,070  ·  21 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0x8ad18e06…472a

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6426

0x34b655…2a6f

6 touches
3 conflicts

0xd12b61a6…95de

0x34b655…2a6f

6 touches
3 conflicts

0xd6113c0f…0a4b

0x34b655…2a6f

6 touches
3 conflicts

0x6b564d99…b9ec

0x34b655…2a6f

4 touches
1 conflict

0xa6b48d6e…0705

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

6 conflicts on slot 0x482471adbb…39122f

← previous block·next block →recent activity