← previous blocknext block →recent activity

Analyzing

Block #74,447,479

34 transactions · 22 stateful · 2026-05-14 02:34:40 UTC

Parallelism

68/100

Blocked

68%

Avg conflicts / tx

1.88

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #74,447,479  ·  34 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

0xf6216d8f…12cf

0xd32edf…ff58

21 touches
55 conflicts

0x4dd1db39…a996

0x188d58…ea8e

6 touches
3 conflicts

0x4dd1db39…a997

0x188d58…ea8e

6 touches
3 conflicts

0x765c236f…ff45

0x2a68ba…90c5

6 touches
3 conflicts

0x4dd1db39…a994

0x188d58…ea8e

6 touches
3 conflicts

0x12309510…0ac2

0x000000…012a

6 touches
3 conflicts

0xf6cc7de8…0b4a

0x3bd359…433a

4 touches
1 conflict

0x00000000…0000

0x63e48b…53f2

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 0xf6216d8f03…3512cf

← previous block·next block →recent activity