Block #73,382,913

← previous blocknext block →recent activity

Analyzing

Block #73,382,913

10 transactions · 10 stateful · 2026-05-09 04:12:08 UTC

Parallelism

60/100

Blocked

30%

Avg conflicts / tx

0.6

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,382,913  ·  10 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x22e295f5…1bef

0x065c9d…c394

4 touches
1 conflict

0xa25e57be…4a15

0x065c9d…c394

3 touches
1 conflict

0xa8ee259b…945c

0x065c9d…c394

3 touches
1 conflict

0xcf6c6d28…b732

0x065c9d…c394

3 touches
1 conflict

0xfee39125…65f3

0x065c9d…c394

2 touches
0 conflicts

0xa7fe0d97…ae1c

0x2a68ba…90c5

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

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity