← previous blocknext block →recent activity

Analyzing

Block #74,407,027

13 transactions · 9 stateful · 2026-05-13 22:05:27 UTC

Parallelism

85/100

Blocked

11%

Avg conflicts / tx

0.08

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,407,027  ·  13 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

0xb3022d4c…8d1b

0x065c9d…c394

4 touches
1 conflict

0x8bf41d0c…9768

0x065c9d…c394

3 touches
1 conflict

0xe64e702b…e0dd

0x065c9d…c394

3 touches
1 conflict

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x41755291…977f

0x065c9d…c394

2 touches
0 conflicts

0x47b807a2…3307

0x065c9d…c394

2 touches
0 conflicts

0x47cd2896…f74d

0x065c9d…c394

2 touches
0 conflicts

0x4f139698…9eda

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

1 conflict on slot 0xb3022d4c4c…d28d1b

← previous block·next block →recent activity