← previous blocknext block →recent activity

Analyzing

Block #74,920,400

37 transactions · 32 stateful · 2026-05-16 07:15:27 UTC

Parallelism

76/100

Blocked

66%

Avg conflicts / tx

1.46

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #74,920,400  ·  37 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0xd9d11313…91f8

0xd32edf…ff58

13 touches
21 conflicts

0x00000000…003d

0x065c9d…c394

10 touches
10 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0xb9868b52…c77f

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x17606ba6…1b6e

0x754704…b603

8 touches
6 conflicts

0xba5743c7…21c4

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

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

21 conflicts on slot 0xd9d1131368…4091f8

← previous block·next block →recent activity