← previous blocknext block →recent activity

Analyzing

Block #74,477,225

12 transactions · 6 stateful · 2026-05-14 05:52:38 UTC

Parallelism

83/100

Blocked

17%

Avg conflicts / tx

0.08

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,477,225  ·  12 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

0x856b5c2e…8484

0x065c9d…c394

4 touches
1 conflict

0xe4aa9a8f…d19c

0x065c9d…c394

3 touches
1 conflict

0x18e502c5…2637

0x065c9d…c394

3 touches
1 conflict

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x14f8406b…fc1f

0x065c9d…c394

2 touches
0 conflicts

0x3c27f6b2…9d08

0x065c9d…c394

2 touches
0 conflicts

0x5c8c6ab6…dc36

0x065c9d…c394

2 touches
0 conflicts

0xffe431af…8faa

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 0x856b5c2e8e…4f8484

← previous block·next block →recent activity