← previous blocknext block →recent activity

Analyzing

Block #74,397,451

13 transactions · 9 stateful · 2026-05-13 21:01:41 UTC

Parallelism

77/100

Blocked

22%

Avg conflicts / tx

0.38

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,397,451  ·  13 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x30276c1c…47b4

0x2a68ba…90c5

6 touches
3 conflicts

0xc514b8f6…9015

0x065c9d…c394

5 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0x01e7b865…6e6d

0x188d58…ea8e

4 touches
1 conflict

0x63904bf5…9c97

0xd32edf…ff58

3 touches
1 conflict

0x6ff13811…cd84

0x065c9d…c394

2 touches
0 conflicts

0x9e9f138b…8782

0x065c9d…c394

2 touches
0 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: 0x2a68ba18…8e90c5

3 conflicts on slot 0x30276c1c08…7247b4

← previous block·next block →recent activity