← previous blocknext block →recent activity

Analyzing

Block #74,279,259

11 transactions · 7 stateful · 2026-05-13 07:55:18 UTC

Parallelism

73/100

Blocked

43%

Avg conflicts / tx

0.36

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,279,259  ·  11 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

0x0d0b2509…074d

0x3bd359…433a

6 touches
3 conflicts

0x17606ba6…1b6e

0x754704…b603

6 touches
3 conflicts

0xe6455d1f…1029

0x754704…b603

6 touches
3 conflicts

0x1b3e5e93…f6c7

0xd32edf…ff58

3 touches
1 conflict

0x448681c4…7335

0x065c9d…c394

2 touches
0 conflicts

0xb9b30717…5c5c

0x065c9d…c394

2 touches
0 conflicts

0xbbee74c2…567a

0x065c9d…c394

2 touches
0 conflicts

0xfa1c63f6…5a5a

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: 0x3bd359c1…15433a

3 conflicts on slot 0x0d0b2509ae…4b074d

← previous block·next block →recent activity