← previous blocknext block →recent activity

Analyzing

Block #74,232,083

9 transactions · 8 stateful · 2026-05-13 02:41:42 UTC

Parallelism

67/100

Blocked

25%

Avg conflicts / tx

0.22

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,232,083  ·  9 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xcf3283ba…c9fa

0x065c9d…c394

4 touches
1 conflict

0x49b576a7…db46

0x065c9d…c394

3 touches
1 conflict

0xfb8c00e4…2f7e

0xd32edf…ff58

3 touches
1 conflict

0x3181ec41…93a6

0x065c9d…c394

2 touches
0 conflicts

0x45a91e02…c331

0x065c9d…c394

2 touches
0 conflicts

0x51594bd6…fa03

0x065c9d…c394

2 touches
0 conflicts

0x58d60d99…e337

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