← previous blocknext block →recent activity

Analyzing

Block #74,429,973

30 transactions · 22 stateful · 2026-05-14 00:38:09 UTC

Parallelism

63/100

Blocked

55%

Avg conflicts / tx

1.9

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #74,429,973  ·  30 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0xfd5ca770…3ec6

0xd32edf…ff58

21 touches
55 conflicts

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0xa1087a5c…66c4

0x754704…b603

8 touches
6 conflicts

0x5a3732cb…edaf

0x1b6862…e19c

8 touches
6 conflicts

0x5adfa8cc…e4a4

0x065c9d…c394

8 touches
6 conflicts

0x30276c1c…47b4

0x2a68ba…90c5

7 touches
6 conflicts

0x00000000…001b

0x1b6862…e19c

4 touches
1 conflict

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

55 conflicts on slot 0xfd5ca77097…433ec6

← previous block·next block →recent activity