Block #73,324,456

← previous blocknext block →recent activity

Analyzing

Block #73,324,456

12 transactions · 10 stateful · 2026-05-08 21:43:22 UTC

Parallelism

58/100

Blocked

40%

Avg conflicts / tx

0.5

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,324,456  ·  12 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

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0xfa44ffbd…695f

0x065c9d…c394

4 touches
1 conflict

0xbd7e37a9…9eb5

0x065c9d…c394

4 touches
1 conflict

0x0df6edb4…07fd

0x065c9d…c394

3 touches
1 conflict

0xd83d482f…34a7

0x065c9d…c394

3 touches
1 conflict

0xa8c8ef05…2cfd

0xd32edf…ff58

3 touches
1 conflict

0xaf9b9f28…2126

0x065c9d…c394

3 touches
1 conflict

0xff23f340…55f1

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

3 conflicts on slot 0x046a928e85…e50012

← previous block·next block →recent activity