← previous blocknext block →recent activity

Analyzing

Block #89,376,836

18 transactions · 17 stateful · 2026-07-22 07:25:06 UTC

Parallelism

83/100

Blocked

41%

Avg conflicts / tx

0.44

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #89,376,836  ·  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

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x0dd44476…ef40

0x34b655…2a6f

6 touches
3 conflicts

0x046740ca…4065

0x34b655…2a6f

4 touches
1 conflict

0x93d4b4e9…5daa

0x851145…3f07

4 touches
1 conflict

0x00000000…00c9

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xd99d25df…ecd8

0x34b655…2a6f

4 touches
1 conflict

0xe3280296…788e

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 0x7e5ea60ab2…b0c4aa

← previous block·next block →recent activity