← previous blocknext block →recent activity

Analyzing

Block #73,956,583

7 transactions · 7 stateful · 2026-05-11 20:06:18 UTC

Parallelism

57/100

Blocked

29%

Avg conflicts / tx

0.29

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,956,583  ·  7 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

0x7301f2af…c48e

0x2a68ba…90c5

4 touches
1 conflict

0x5d9cfbb6…faba

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x7c6fe047…301c

0x065c9d…c394

3 touches
1 conflict

0x0b4ee455…c576

0x065c9d…c394

3 touches
1 conflict

0xd7c5a75a…adb6

0x065c9d…c394

2 touches
0 conflicts

0x00000000…0012

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…001a

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: 0x2a68ba18…8e90c5

1 conflict on slot 0x7301f2af71…f4c48e

← previous block·next block →recent activity