← previous blocknext block →recent activity

Analyzing

Block #73,650,613

14 transactions · 13 stateful · 2026-05-10 09:55:19 UTC

Parallelism

79/100

Blocked

31%

Avg conflicts / tx

0.29

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,650,613  ·  14 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

0xed57bddf…1abf

0xc8689a…ee79

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xf0f673fd…37a7

0x6c4bfa…a540

4 touches
1 conflict

0x8a35acfb…d1aa

0x8d66a4…3095

4 touches
1 conflict

0xfff38d9f…7063

0x8d66a4…3095

4 touches
1 conflict

0x7f81fb82…633e

0x065c9d…c394

4 touches
1 conflict

0xa271597a…a02f

0x065c9d…c394

4 touches
1 conflict

0xeb50d04f…39f8

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: 0xc8689a47…62ee79

1 conflict on slot 0xed57bddf8e…bd1abf

← previous block·next block →recent activity