← previous blocknext block →recent activity

Analyzing

Block #73,476,407

12 transactions · 7 stateful · 2026-05-09 14:34:21 UTC

Parallelism

75/100

Blocked

29%

Avg conflicts / tx

0.25

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,476,407  ·  12 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

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x630a647d…2d68

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xd84d1890…cd9e

0x065c9d…c394

4 touches
1 conflict

0x2e4499b9…6d34

0x065c9d…c394

2 touches
0 conflicts

0x3e1c59c7…6906

0x065c9d…c394

2 touches
0 conflicts

0x63bc4a18…c06a

0x065c9d…c394

2 touches
0 conflicts

0x6ea2637f…ee8c

0x065c9d…c394

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

1 conflict on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity