← previous blocknext block →recent activity

Analyzing

Block #73,464,309

8 transactions · 8 stateful · 2026-05-09 13:13:52 UTC

Parallelism

38/100

Blocked

50%

Avg conflicts / tx

1.13

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,464,309  ·  8 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

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x22e295f5…1bef

0x065c9d…c394

6 touches
3 conflicts

0x17f7beda…0b68

0x065c9d…c394

4 touches
1 conflict

0x1ca9e6f1…2a1c

0x065c9d…c394

3 touches
1 conflict

0xcc0423f3…21f7

0x065c9d…c394

3 touches
1 conflict

0x244ee2e5…400c

0x065c9d…c394

3 touches
1 conflict

0x33ac0021…d4fc

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

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity