Block #73,480,898

← previous blocknext block →recent activity

Analyzing

Block #73,480,898

12 transactions · 9 stateful · 2026-05-09 15:04:12 UTC

Parallelism

83/100

Blocked

22%

Avg conflicts / tx

0.33

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,480,898  ·  12 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

0x6f08361d…bda6

0x065c9d…c394

4 touches
1 conflict

0x796621be…b343

0x065c9d…c394

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0xca96d038…dfb1

0x065c9d…c394

3 touches
1 conflict

0xb3c6b273…6e43

0x065c9d…c394

3 touches
1 conflict

0x1acaa26f…7b77

0x34b655…2a6f

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 0x6f08361da9…89bda6

← previous block·next block →recent activity