← previous blocknext block →recent activity

Analyzing

Block #73,668,791

12 transactions · 8 stateful · 2026-05-10 11:57:53 UTC

Parallelism

75/100

Blocked

38%

Avg conflicts / tx

0.25

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,668,791  ·  12 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

0x3e4281f8…f9a6

0x065c9d…c394

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x68e82d8d…1965

0xd32edf…ff58

3 touches
1 conflict

0x33b282a7…3845

0x065c9d…c394

3 touches
1 conflict

0xfb11e446…a991

0x065c9d…c394

3 touches
1 conflict

0x003d145b…9ee1

0x065c9d…c394

2 touches
0 conflicts

0x51e2e104…a424

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 0x3e4281f88e…eaf9a6

← previous block·next block →recent activity