← previous blocknext block →recent activity

Analyzing

Block #73,396,281

13 transactions · 11 stateful · 2026-05-09 05:41:07 UTC

Parallelism

85/100

Blocked

9%

Avg conflicts / tx

0.08

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,396,281  ·  13 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

0x22e295f5…1bef

0x065c9d…c394

4 touches
1 conflict

0x4d87512b…897c

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x29aa692d…1d8d

0x065c9d…c394

2 touches
0 conflicts

0x2bc4380d…eccb

0x065c9d…c394

2 touches
0 conflicts

0x411fd21d…9dd7

0x065c9d…c394

2 touches
0 conflicts

0x46f4e421…e0c2

0x065c9d…c394

2 touches
0 conflicts

0x59be504c…695e

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 0x22e295f5d8…ac1bef

← previous block·next block →recent activity