Block #73,643,917

← previous blocknext block →recent activity

Analyzing

Block #73,643,917

10 transactions · 6 stateful · 2026-05-10 09:10:14 UTC

Parallelism

70/100

Blocked

33%

Avg conflicts / tx

0.3

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,643,917  ·  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

0x22e295f5…1bef

0x065c9d…c394

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x2dbaa2ec…a19c

0x065c9d…c394

4 touches
1 conflict

0xa8ee259b…945c

0x065c9d…c394

3 touches
1 conflict

0x095db123…c940

0x065c9d…c394

3 touches
1 conflict

0xa5804f7b…cc1b

0x065c9d…c394

3 touches
1 conflict

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x4d87512b…897c

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