Block #73,273,723

← previous blocknext block →recent activity

Analyzing

Block #73,273,723

10 transactions · 9 stateful · 2026-05-08 16:05:44 UTC

Parallelism

60/100

Blocked

33%

Avg conflicts / tx

0.9

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,273,723  ·  10 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xbd7e37a9…9eb5

0x065c9d…c394

8 touches
6 conflicts

0x046a928e…0012

0x2a68ba…90c5

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x23e93d7d…f0fb

0x000000…012a

2 touches
0 conflicts

0x4d8d472e…564b

0x065c9d…c394

2 touches
0 conflicts

0x4783dace…37bc

0x3bd359…433a

2 touches
0 conflicts

0x64ddb9ef…ebe2

0x3bd359…433a

2 touches
0 conflicts

0x00000000…0002

0x579275…008a

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

6 conflicts on slot 0xbd7e37a9b5…859eb5

← previous block·next block →recent activity