← previous blocknext block →recent activity

Analyzing

Block #72,984,414

22 transactions · 21 stateful · 2026-05-07 08:01:03 UTC

Parallelism

64/100

Blocked

52%

Avg conflicts / tx

1.27

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #72,984,414  ·  22 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x17606ba6…1b6e

0x754704…b603

10 touches
10 conflicts

0x00000000…003d

0x065c9d…c394

10 touches
10 conflicts

0x92d610a6…9a40

0x2a68ba…90c5

8 touches
6 conflicts

0x0b390c61…dc07

0x065c9d…c394

8 touches
6 conflicts

0x13b3ee7a…b0e1

0xd32edf…ff58

7 touches
6 conflicts

0xdf766d52…fcca

0x065c9d…c394

7 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

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: USDC (USDC)

10 conflicts on slot 0x17606ba612…ea1b6e

← previous block·next block →recent activity