← previous blocknext block →recent activity

Analyzing

Block #74,679,490

9 transactions · 8 stateful · 2026-05-15 04:27:30 UTC

Parallelism

78/100

Blocked

38%

Avg conflicts / tx

0.33

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,679,490  ·  9 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x78b53e9b…0fea

0x065c9d…c394

4 touches
1 conflict

0x41755291…977f

0x065c9d…c394

4 touches
1 conflict

0x47b807a2…3307

0x065c9d…c394

4 touches
1 conflict

0x53785046…f318

0x065c9d…c394

4 touches
1 conflict

0x9ea7f021…f49c

0x065c9d…c394

3 touches
1 conflict

0x93fe9669…0d9c

0x065c9d…c394

3 touches
1 conflict

0xc04dd329…f4c1

0x065c9d…c394

3 touches
1 conflict

0x92d610a6…9a40

0x2a68ba…90c5

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: 0x065c9d28…a9c394

1 conflict on slot 0x78b53e9b3f…f20fea

← previous block·next block →recent activity