← previous blocknext block →recent activity

Analyzing

Block #89,669,305

17 transactions · 17 stateful · 2026-07-23 15:38:55 UTC

Parallelism

82/100

Blocked

35%

Avg conflicts / tx

0.47

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #89,669,305  ·  17 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

0x6fe7d366…78ff

0x34b655…2a6f

6 touches
3 conflicts

0x1fdc16cf…015e

0x34b655…2a6f

6 touches
3 conflicts

0x6cfabf20…d256

0x34b655…2a6f

6 touches
3 conflicts

0x7c0bdc54…9dde

0x34b655…2a6f

4 touches
1 conflict

0xa80684c9…3948

0x34b655…2a6f

4 touches
1 conflict

0xb11a3969…fc6a

0x34b655…2a6f

4 touches
1 conflict

0xb9b4eff6…c3ef

0x34b655…2a6f

4 touches
1 conflict

0xbcbf5d09…8bac

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 0x6fe7d366be…a578ff

← previous block·next block →recent activity