← previous blocknext block →recent activity

Analyzing

Block #89,743,582

15 transactions · 13 stateful · 2026-07-23 21:54:17 UTC

Parallelism

73/100

Blocked

62%

Avg conflicts / tx

0.87

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #89,743,582  ·  15 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xe8d8a9a2…40f3

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x53d1be2f…a549

0xd32edf…ff58

5 touches
3 conflicts

0x00000000…001d

0x1b6862…e19c

4 touches
1 conflict

0x00000000…002d

0x1b6862…e19c

4 touches
1 conflict

0xada193dc…5c7e

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

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

3 conflicts on slot 0xe8d8a9a263…f840f3

← previous block·next block →recent activity