← previous blocknext block →recent activity

Analyzing

Block #73,970,306

9 transactions · 7 stateful · 2026-05-11 21:37:36 UTC

Parallelism

78/100

Blocked

14%

Avg conflicts / tx

0.11

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,970,306  ·  9 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

0xc35c017f…15df

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x3e5b67af…6a7c

0x065c9d…c394

3 touches
1 conflict

0x1edc05c5…d874

0x065c9d…c394

2 touches
0 conflicts

0x1f9b4577…35c8

0x065c9d…c394

2 touches
0 conflicts

0x786ad8d6…5180

0x065c9d…c394

2 touches
0 conflicts

0xfe0483cb…686c

0x065c9d…c394

2 touches
0 conflicts

0x00000000…0012

0x1b6862…e19c

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 0xc35c017f81…bf15df

← previous block·next block →recent activity