← previous blocknext block →recent activity

Analyzing

Block #89,538,054

21 transactions · 17 stateful · 2026-07-23 01:22:19 UTC

Parallelism

71/100

Blocked

47%

Avg conflicts / tx

0.52

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #89,538,054  ·  21 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

0x8267cc91…78bc

0x34b655…2a6f

6 touches
3 conflicts

0x861e5aef…d32c

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x92385428…6941

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0xa5ab7b8a…c97b

0x34b655…2a6f

4 touches
1 conflict

0xc3656cd1…8269

0x34b655…2a6f

4 touches
1 conflict

0xd8834cf3…0004

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 0x8267cc9168…1278bc

← previous block·next block →recent activity