← previous blocknext block →recent activity

Analyzing

Block #74,920,435

28 transactions · 20 stateful · 2026-05-16 07:15:41 UTC

Parallelism

75/100

Blocked

70%

Avg conflicts / tx

1.36

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,920,435  ·  28 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

0x60f7fbaf…bd58

0x34b655…2a6f

10 touches
10 conflicts

0x30276c1c…47b4

0x2a68ba…90c5

10 touches
10 conflicts

0xe440e6cb…104e

0xd32edf…ff58

9 touches
10 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0xea02471d…1542

0x34b655…2a6f

8 touches
6 conflicts

0xba5743c7…21c4

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0xbef92037…799a

0x065c9d…c394

7 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 0x60f7fbaf90…97bd58

← previous block·next block →recent activity