← previous blocknext block →recent activity

Analyzing

Block #73,921,151

26 transactions · 23 stateful · 2026-05-11 16:10:37 UTC

Parallelism

77/100

Blocked

65%

Avg conflicts / tx

1.38

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,921,151  ·  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

0xee230b20…5a0f

0x34b655…2a6f

10 touches
10 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

10 touches
10 conflicts

0x6eba5e7f…4b52

0x34b655…2a6f

10 touches
10 conflicts

0xac8e97a0…8426

0x34b655…2a6f

10 touches
10 conflicts

0x96844849…b4b0

0x34b655…2a6f

10 touches
10 conflicts

0x54f1fe63…fada

0xd32edf…ff58

9 touches
10 conflicts

0x8db1e0f2…2fcf

0x34b655…2a6f

8 touches
6 conflicts

0xf537eaa0…73c8

0x065c9d…c394

8 touches
6 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: 0x34b6552d…112a6f

10 conflicts on slot 0xee230b202a…c05a0f

← previous block·next block →recent activity