← previous blocknext block →recent activity

Analyzing

Block #89,526,550

26 transactions · 22 stateful · 2026-07-23 00:05:37 UTC

Parallelism

77/100

Blocked

36%

Avg conflicts / tx

0.65

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #89,526,550  ·  26 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

6 touches
3 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

6 touches
3 conflicts

0x1fdc16cf…015e

0x34b655…2a6f

6 touches
3 conflicts

0xcc99ae0a…075a

0x34b655…2a6f

6 touches
3 conflicts

0x326a02b5…8dad

0x34b655…2a6f

6 touches
3 conflicts

0xdb42d6d8…5e64

0x34b655…2a6f

5 touches
3 conflicts

0x9c5ce778…4b6a

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

10 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity