← previous blocknext block →recent activity

Analyzing

Block #89,570,228

18 transactions · 17 stateful · 2026-07-23 04:57:20 UTC

Parallelism

83/100

Blocked

12%

Avg conflicts / tx

0.17

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #89,570,228  ·  18 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xa5ab7b8a…c97b

0x34b655…2a6f

6 touches
3 conflicts

0x69411fb3…e36d

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4aa

0x34b655…2a6f

4 touches
1 conflict

0x92385428…6941

0x34b655…2a6f

4 touches
1 conflict

0xa013ecc1…7c8f

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0x2d071de0…c86e

0x34b655…2a6f

4 touches
1 conflict

0x64aaadbf…f9f3

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

3 conflicts on slot 0xa5ab7b8a6d…b0c97b

← previous block·next block →recent activity