← previous blocknext block →recent activity

Analyzing

Block #73,016,287

7 transactions · 7 stateful · 2026-05-07 11:32:53 UTC

Parallelism

71/100

Blocked

14%

Avg conflicts / tx

0.14

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,016,287  ·  7 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

0x0b390c61…dc07

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x5111b16b…bebc

0x065c9d…c394

3 touches
1 conflict

0x0d4f1d65…2005

0x065c9d…c394

2 touches
0 conflicts

0x3f478af2…1a8b

0x065c9d…c394

2 touches
0 conflicts

0x4e2c1187…7831

0x065c9d…c394

2 touches
0 conflicts

0x503ee695…ff73

0x065c9d…c394

2 touches
0 conflicts

0xbd7e37a9…9eb5

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 0x0b390c6160…02dc07

← previous block·next block →recent activity