← previous blocknext block →recent activity

Analyzing

Block #74,471,449

13 transactions · 8 stateful · 2026-05-14 05:14:13 UTC

Parallelism

85/100

Blocked

13%

Avg conflicts / tx

0.08

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,471,449  ·  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

0x5c8c6ab6…dc36

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x28cc3374…7409

0x065c9d…c394

2 touches
0 conflicts

0x626198ba…e145

0x065c9d…c394

2 touches
0 conflicts

0x8003954c…0e3d

0x065c9d…c394

2 touches
0 conflicts

0x96582f1f…7033

0x065c9d…c394

2 touches
0 conflicts

0xd4ca6582…7f87

0x065c9d…c394

2 touches
0 conflicts

0xec6a2711…9ff8

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 0x5c8c6ab6f0…86dc36

← previous block·next block →recent activity