Block #73,382,748

← previous blocknext block →recent activity

Analyzing

Block #73,382,748

19 transactions · 17 stateful · 2026-05-09 04:11:02 UTC

Parallelism

74/100

Blocked

35%

Avg conflicts / tx

0.47

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,382,748  ·  19 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

0xb159af88…a9e7

0x065c9d…c394

8 touches
6 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x8a2657f5…e008

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x00000000…0002

0xab3526…fa38

4 touches
1 conflict

0xa7fe0d97…ae1c

0x2a68ba…90c5

4 touches
1 conflict

0xb4689f56…9b8e

0x065c9d…c394

3 touches
1 conflict

0x8728cf1c…4751

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: 0x065c9d28…a9c394

6 conflicts on slot 0xb159af880b…47a9e7

← previous block·next block →recent activity