← previous blocknext block →recent activity

Analyzing

Block #73,868,214

9 transactions · 7 stateful · 2026-05-11 10:17:58 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,868,214  ·  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

0x22ef1e0b…b650

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xb928c148…2f0d

0x065c9d…c394

3 touches
1 conflict

0x12d760d9…c6cb

0x065c9d…c394

3 touches
1 conflict

0x77c97d49…1f7b

0x065c9d…c394

2 touches
0 conflicts

0x7cd96472…ffbd

0x065c9d…c394

2 touches
0 conflicts

0x7f81fb82…633e

0x065c9d…c394

2 touches
0 conflicts

0xf8b759c9…3c98

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 0x22ef1e0be2…40b650

← previous block·next block →recent activity