← previous blocknext block →recent activity

Analyzing

Block #73,029,596

14 transactions · 12 stateful · 2026-05-07 13:01:29 UTC

Parallelism

79/100

Blocked

33%

Avg conflicts / tx

0.43

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,029,596  ·  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

0x70b2f813…783c

0x2a68ba…90c5

6 touches
3 conflicts

0x744d5f8f…d00a

0xd32edf…ff58

5 touches
3 conflicts

0x12408929…08d2

0x065c9d…c394

4 touches
3 conflicts

0xbd7e37a9…9eb5

0x065c9d…c394

4 touches
1 conflict

0xfd0bab67…1154

0x065c9d…c394

4 touches
1 conflict

0x00000000…000b

0x6ca43f…c331

4 touches
1 conflict

0x6866eec1…6af4

0x065c9d…c394

4 touches
1 conflict

0x8f956fd4…9235

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

3 conflicts on slot 0x70b2f81398…04783c

← previous block·next block →recent activity