← previous blocknext block →recent activity

Analyzing

Block #89,547,501

22 transactions · 21 stateful · 2026-07-23 02:25:28 UTC

Parallelism

73/100

Blocked

43%

Avg conflicts / tx

0.68

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #89,547,501  ·  22 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

0xaad704fb…e3c2

0x34b655…2a6f

6 touches
3 conflicts

0x64aaadbf…f9f3

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x4886b3df…67a3

0x34b655…2a6f

6 touches
3 conflicts

0x4590830b…1bce

0x34b655…2a6f

4 touches
1 conflict

0x48203298…65cb

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x4e089204…52fb

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 0xaad704fbd8…27e3c2

← previous block·next block →recent activity