← previous blocknext block →recent activity

Analyzing

Block #73,353,052

11 transactions · 11 stateful · 2026-05-09 00:53:38 UTC

Parallelism

73/100

Blocked

18%

Avg conflicts / tx

0.27

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,353,052  ·  11 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

0x4d87512b…897c

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x1fec95ff…d032

0x065c9d…c394

4 touches
1 conflict

0x319d2111…5ecc

0x065c9d…c394

4 touches
1 conflict

0x422f85e2…50f8

0x065c9d…c394

4 touches
1 conflict

0x6e4df948…617b

0x065c9d…c394

4 touches
1 conflict

0xa330322d…5c58

0x065c9d…c394

4 touches
1 conflict

0xc84d2d1d…d97d

0x065c9d…c394

4 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

3 conflicts on slot 0x4d87512b00…43897c

← previous block·next block →recent activity