← previous blocknext block →recent activity

Analyzing

Block #74,609,366

30 transactions · 19 stateful · 2026-05-14 20:39:50 UTC

Parallelism

83/100

Blocked

58%

Avg conflicts / tx

0.73

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,609,366  ·  30 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x17606ba6…1b6e

0x754704…b603

8 touches
6 conflicts

0x834ceaa9…66d7

0xd32edf…ff58

7 touches
6 conflicts

0x01e7b865…6e6d

0x188d58…ea8e

6 touches
3 conflicts

0x56a919c4…ab49

0xee8c0e…1242

6 touches
3 conflicts

0xd025d7d7…f05a

0x3bd359…433a

6 touches
3 conflicts

0xffe431af…8faa

0x065c9d…c394

4 touches
1 conflict

0x5c8c6ab6…dc36

0x065c9d…c394

4 touches
1 conflict

0x01e7b865…6e6f

0x188d58…ea8e

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: 0x754704bc…afb603

6 conflicts on slot 0x17606ba612…ea1b6e

← previous block·next block →recent activity