← previous blocknext block →recent activity

Analyzing

Block #89,666,313

16 transactions · 14 stateful · 2026-07-23 15:23:36 UTC

Parallelism

81/100

Blocked

36%

Avg conflicts / tx

0.44

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #89,666,313  ·  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

0x99c5409a…25b7

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x4577624d…1597

0x34b655…2a6f

4 touches
1 conflict

0xe833d959…8666

0x34b655…2a6f

4 touches
1 conflict

0xefd234e9…5b03

0x34b655…2a6f

4 touches
1 conflict

0xf324b405…ca30

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x6ca0994e…02ef

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 0x99c5409a28…0025b7

← previous block·next block →recent activity