Block #73,396,118

← previous blocknext block →recent activity

Analyzing

Block #73,396,118

23 transactions · 18 stateful · 2026-05-09 05:40:02 UTC

Parallelism

78/100

Blocked

39%

Avg conflicts / tx

0.65

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,396,118  ·  23 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

10 touches
10 conflicts

0x22e295f5…1bef

0x065c9d…c394

10 touches
10 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xc38e9f75…9508

0xd32edf…ff58

5 touches
3 conflicts

0xe75ce681…ba60

0x188d58…ea8e

4 touches
1 conflict

0x6af306bb…2e81

0x3bd359…433a

4 touches
1 conflict

0x09beabbc…065c

0x188d58…ea8e

4 touches
1 conflict

0x09beabbc…065e

0x188d58…ea8e

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

10 conflicts on slot 0x046a928e85…e50012

← previous block·next block →recent activity