← previous blocknext block →recent activity

Analyzing

Block #73,041,809

45 transactions · 33 stateful · 2026-05-07 14:22:46 UTC

Parallelism

76/100

Blocked

52%

Avg conflicts / tx

1.58

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #73,041,809  ·  45 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0xecbb3fa4…e3be

0xd32edf…ff58

21 touches
55 conflicts

0x17606ba6…1b6e

0x754704…b603

10 touches
10 conflicts

0x01e7b865…6e6d

0x188d58…ea8e

8 touches
6 conflicts

0x01e7b865…6e6f

0x188d58…ea8e

8 touches
6 conflicts

0x874cb67f…26e1

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x3b8ffd61…f3ad

0x34b655…2a6f

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: 0xd32edf66…9fff58

55 conflicts on slot 0xecbb3fa407…c2e3be

← previous block·next block →recent activity