← previous blocknext block →recent activity

Analyzing

Block #89,568,397

14 transactions · 14 stateful · 2026-07-23 04:45:05 UTC

Parallelism

86/100

Blocked

14%

Avg conflicts / tx

0.14

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #89,568,397  ·  14 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x266a6b2c…4377

0x34b655…2a6f

4 touches
1 conflict

0x274ac476…27fa

0x34b655…2a6f

4 touches
1 conflict

0x342f88f5…2a06

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4aa

0x34b655…2a6f

4 touches
1 conflict

0x92385428…6941

0x34b655…2a6f

4 touches
1 conflict

0xd708bac6…2e5d

0x34b655…2a6f

4 touches
1 conflict

0xd7d3e7dd…2bf3

0x34b655…2a6f

4 touches
1 conflict

0x889d5e90…929a

0x2a68ba…90c5

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

1 conflict on slot 0x266a6b2c33…a14377

← previous block·next block →recent activity