← previous blocknext block →recent activity

Analyzing

Block #89,750,826

15 transactions · 14 stateful · 2026-07-23 22:30:54 UTC

Parallelism

87/100

Blocked

14%

Avg conflicts / tx

0.2

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #89,750,826  ·  15 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

0xc824469a…6426

0x34b655…2a6f

4 touches
1 conflict

0xfc3d5171…8357

0x34b655…2a6f

4 touches
1 conflict

0xfcbae679…689a

0x34b655…2a6f

4 touches
1 conflict

0x889d5e90…929a

0x2a68ba…90c5

4 touches
1 conflict

0x04e17b28…d9ef

0x34b655…2a6f

4 touches
1 conflict

0x04e17b28…d9f0

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x53699236…fede

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

1 conflict on slot 0xc824469a90…af6426

← previous block·next block →recent activity