← previous blocknext block →recent activity

Analyzing

Block #74,338,150

14 transactions · 9 stateful · 2026-05-13 14:27:07 UTC

Parallelism

86/100

Blocked

11%

Avg conflicts / tx

0.07

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,338,150  ·  14 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

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xf96d5064…3718

0x065c9d…c394

4 touches
1 conflict

0xfb832e99…18ed

0x065c9d…c394

3 touches
1 conflict

0x48c0a16d…cca4

0x065c9d…c394

2 touches
0 conflicts

0x5c8c6ab6…dc36

0x065c9d…c394

2 touches
0 conflicts

0x67485125…eaa4

0x065c9d…c394

2 touches
0 conflicts

0x7354cf3a…f270

0x065c9d…c394

2 touches
0 conflicts

0x81f76c8c…a0c7

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 0x0000000000…00003d

← previous block·next block →recent activity