← previous blocknext block →recent activity

Analyzing

Block #74,450,253

34 transactions · 24 stateful · 2026-05-14 02:53:10 UTC

Parallelism

79/100

Blocked

54%

Avg conflicts / tx

1

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,450,253  ·  34 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

0x4d0b6df7…9e19

0xd32edf…ff58

13 touches
21 conflicts

0x00000000…0000

0xcc67aa…c71c

10 touches
10 conflicts

0x00000000…0001

0xcc67aa…c71c

10 touches
10 conflicts

0xa472d565…9fe4

0x3bd359…433a

10 touches
10 conflicts

0x44ad89ba…cf83

0x5c2513…7777

10 touches
10 conflicts

0xce2b6650…ecc3

0x5c2513…7777

10 touches
10 conflicts

0x00c46468…f328

0x3bd359…433a

10 touches
10 conflicts

0xba5743c7…21c2

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

21 conflicts on slot 0x4d0b6df738…4f9e19

← previous block·next block →recent activity