← previous blocknext block →recent activity

Analyzing

Block #89,587,430

19 transactions · 18 stateful · 2026-07-23 06:52:09 UTC

Parallelism

74/100

Blocked

39%

Avg conflicts / tx

0.74

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #89,587,430  ·  19 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x00000000…0006

0x0a2fbf…29b1

10 touches
10 conflicts

0x2c9e115f…48d8

0x0a2fbf…29b1

10 touches
10 conflicts

0x2c9e115f…48d9

0x0a2fbf…29b1

10 touches
10 conflicts

0xfae79884…8f31

0x0a2fbf…29b1

10 touches
10 conflicts

0xfae79884…8f32

0x0a2fbf…29b1

10 touches
10 conflicts

0xfae79884…8f35

0x0a2fbf…29b1

10 touches
10 conflicts

0x00000000…0005

0x370e2e…63b4

10 touches
10 conflicts

0x01876b21…9083

0x370e2e…63b4

10 touches
10 conflicts

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: 0x0a2fbf2d…f729b1

10 conflicts on slot 0x0000000000…000006

← previous block·next block →recent activity