Block #73,639,021

← previous blocknext block →recent activity

Analyzing

Block #73,639,021

13 transactions · 11 stateful · 2026-05-10 08:37:16 UTC

Parallelism

62/100

Blocked

55%

Avg conflicts / tx

1.31

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,639,021  ·  13 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x4d87512b…897c

0x065c9d…c394

10 touches
10 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0xae6e010b…1397

0x065c9d…c394

4 touches
1 conflict

0x44d4e3d9…eec7

0x065c9d…c394

4 touches
1 conflict

0xf771f551…01ff

0x065c9d…c394

3 touches
1 conflict

0x5168fdc1…fcc5

0x065c9d…c394

3 touches
1 conflict

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

10 conflicts on slot 0x4d87512b00…43897c

← previous block·next block →recent activity