Block #73,649,191

← previous blocknext block →recent activity

Analyzing

Block #73,649,191

10 transactions · 10 stateful · 2026-05-10 09:45:45 UTC

Parallelism

70/100

Blocked

20%

Avg conflicts / tx

0.2

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,649,191  ·  10 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

0xc9e97522…3519

0x2a68ba…90c5

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0xfd24abbc…ef84

0x065c9d…c394

3 touches
1 conflict

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x06155188…dbd2

0x065c9d…c394

2 touches
0 conflicts

0x07c452cb…1224

0x065c9d…c394

2 touches
0 conflicts

0x1a43c714…05bf

0x065c9d…c394

2 touches
0 conflicts

0x4df066c0…e7c4

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

1 conflict on slot 0xc9e9752290…9c3519

← previous block·next block →recent activity