Block #73,202,616

← previous blocknext block →recent activity

Analyzing

Block #73,202,616

12 transactions · 10 stateful · 2026-05-08 08:12:45 UTC

Parallelism

75/100

Blocked

30%

Avg conflicts / tx

0.5

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,202,616  ·  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

6 touches
3 conflicts

0x671f46bc…b926

0x065c9d…c394

4 touches
1 conflict

0x5fd11b4f…d470

0x065c9d…c394

4 touches
1 conflict

0x3b8ffd61…f3ad

0x34b655…2a6f

4 touches
1 conflict

0x99ac85bf…888f

0x065c9d…c394

3 touches
1 conflict

0xbe1e4d0f…69cd

0x065c9d…c394

3 touches
1 conflict

0xc89923b6…7cb6

0x065c9d…c394

3 touches
1 conflict

0xd33b101f…4b42

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