← previous blocknext block →recent activity

Analyzing

Block #73,977,633

21 transactions · 17 stateful · 2026-05-11 22:26:50 UTC

Parallelism

71/100

Blocked

53%

Avg conflicts / tx

1.1

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,977,633  ·  21 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

0x62b86eef…8ec3

0xd32edf…ff58

11 touches
15 conflicts

0x17606ba6…1b6e

0x754704…b603

8 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0xe75ce681…ba5f

0x188d58…ea8e

6 touches
3 conflicts

0x00000000…001a

0x1b6862…e19c

6 touches
3 conflicts

0xe75ce681…ba61

0x188d58…ea8e

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

6 touches
3 conflicts

0xcb45d9d6…cb82

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 0x62b86eef7d…df8ec3

← previous block·next block →recent activity