← previous blocknext block →recent activity

Analyzing

Block #73,359,668

10 transactions · 9 stateful · 2026-05-09 01:37:28 UTC

Parallelism

60/100

Blocked

44%

Avg conflicts / tx

0.6

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,359,668  ·  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

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x399082fb…efd8

0x065c9d…c394

4 touches
1 conflict

0x6abb10c5…aa05

0x065c9d…c394

4 touches
1 conflict

0xe17cd15e…0c83

0x065c9d…c394

4 touches
1 conflict

0xc5f38257…41ae

0x065c9d…c394

3 touches
1 conflict

0x2bbcb79c…e696

0x065c9d…c394

3 touches
1 conflict

0x865bcac4…b381

0x065c9d…c394

3 touches
1 conflict

0xcfc3140d…5db1

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: 0x2a68ba18…8e90c5

3 conflicts on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity