← previous blocknext block →recent activity

Analyzing

Block #73,436,077

22 transactions · 18 stateful · 2026-05-09 10:05:55 UTC

Parallelism

73/100

Blocked

56%

Avg conflicts / tx

1.09

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,436,077  ·  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

0xf55ce140…6dbf

0xd32edf…ff58

11 touches
15 conflicts

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0xd59f6ed1…03eb

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x6f08361d…bda6

0x065c9d…c394

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…002f

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0012

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

15 conflicts on slot 0xf55ce1406e…6f6dbf

← previous block·next block →recent activity