← previous blocknext block →recent activity

Analyzing

Block #89,587,446

16 transactions · 15 stateful · 2026-07-23 06:52:16 UTC

Parallelism

81/100

Blocked

27%

Avg conflicts / tx

0.56

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #89,587,446  ·  16 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

0xb4d0dec1…7318

0x34b655…2a6f

6 touches
3 conflicts

0x64aaadbf…f9f3

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x3ea25e92…a36d

0x34b655…2a6f

4 touches
1 conflict

0x5c16527f…628c

0x34b655…2a6f

4 touches
1 conflict

0x601a8e1c…99e2

0x34b655…2a6f

4 touches
1 conflict

0x69d0a300…67ef

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

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 0xb4d0dec1cc…fb7318

← previous block·next block →recent activity