← previous blocknext block →recent activity

Analyzing

Block #74,433,244

38 transactions · 29 stateful · 2026-05-14 01:00:01 UTC

Parallelism

76/100

Blocked

59%

Avg conflicts / tx

0.89

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #74,433,244  ·  38 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

0xfc96eb6d…418e

0xd32edf…ff58

13 touches
21 conflicts

0x01e7b865…6e6e

0x188d58…ea8e

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0x01e7b865…6e6d

0x188d58…ea8e

6 touches
3 conflicts

0xd5b10148…e634

0x1b6862…e19c

4 touches
1 conflict

0x30276c1c…47b4

0x2a68ba…90c5

4 touches
1 conflict

0x7c403af1…31b1

0x3bd359…433a

4 touches
1 conflict

0xdd70bea3…1ffe

0x3bd359…433a

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

21 conflicts on slot 0xfc96eb6dbe…fc418e

← previous block·next block →recent activity