← previous blocknext block →recent activity

Analyzing

Block #73,789,879

11 transactions · 9 stateful · 2026-05-11 01:35:03 UTC

Parallelism

64/100

Blocked

33%

Avg conflicts / tx

0.73

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,789,879  ·  11 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

0x17606ba6…1b6e

0x754704…b603

8 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0x78694995…f66d

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…002e

0x1b6862…e19c

6 touches
3 conflicts

0xe75ce681…ba5f

0x188d58…ea8e

6 touches
3 conflicts

0xe75ce681…ba61

0x188d58…ea8e

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 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: 0x754704bc…afb603

6 conflicts on slot 0x17606ba612…ea1b6e

← previous block·next block →recent activity