← previous blocknext block →recent activity

Analyzing

Block #73,869,129

23 transactions · 18 stateful · 2026-05-11 10:24:03 UTC

Parallelism

70/100

Blocked

61%

Avg conflicts / tx

1.3

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #73,869,129  ·  23 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xcd3c2cbb…e72d

0xd32edf…ff58

11 touches
15 conflicts

0x5de96bd3…c60c

0x34b655…2a6f

10 touches
10 conflicts

0x00000000…0018

0x1b6862…e19c

10 touches
10 conflicts

0xcb45d9d6…cb80

0x1b6862…e19c

10 touches
10 conflicts

0x2f387761…308c

0x34b655…2a6f

8 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0012

0x1b6862…e19c

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

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

15 conflicts on slot 0xcd3c2cbb70…1ae72d

← previous block·next block →recent activity