← previous blocknext block →recent activity

Analyzing

Block #74,377,211

19 transactions · 9 stateful · 2026-05-13 18:46:55 UTC

Parallelism

84/100

Blocked

33%

Avg conflicts / tx

0.21

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,377,211  ·  19 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

0xace50de0…6e90

0xd32edf…ff58

5 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x6b7cca1e…5cc2

0x065c9d…c394

3 touches
1 conflict

0x1336aebc…f805

0x065c9d…c394

2 touches
0 conflicts

0x41755291…977f

0x065c9d…c394

2 touches
0 conflicts

0x47b807a2…3307

0x065c9d…c394

2 touches
0 conflicts

0xca61af06…81e7

0x065c9d…c394

2 touches
0 conflicts

0xcee0e292…66e9

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: 0xd32edf66…9fff58

3 conflicts on slot 0xace50de03f…886e90

← previous block·next block →recent activity