← previous blocknext block →recent activity

Analyzing

Block #73,049,667

26 transactions · 19 stateful · 2026-05-07 15:15:10 UTC

Parallelism

77/100

Blocked

68%

Avg conflicts / tx

1.31

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,049,667  ·  26 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

0xa628088f…5eac

0xd32edf…ff58

11 touches
15 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0x251861eb…78fd

0x34b655…2a6f

6 touches
3 conflicts

0x2cf96c0a…538a

0x34b655…2a6f

6 touches
3 conflicts

0x388e001a…7e04

0x34b655…2a6f

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0x7cbd466f…1700

0x34b655…2a6f

6 touches
3 conflicts

0xf853eb8e…4027

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

15 conflicts on slot 0xa628088fdf…c25eac

← previous block·next block →recent activity