Block #73,333,729

← previous blocknext block →recent activity

Analyzing

Block #73,333,729

15 transactions · 12 stateful · 2026-05-08 22:45:01 UTC

Parallelism

60/100

Blocked

42%

Avg conflicts / tx

1.2

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,333,729  ·  15 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x00000000…003d

0x065c9d…c394

10 touches
10 conflicts

0x046a928e…0012

0x2a68ba…90c5

10 touches
10 conflicts

0xf537eaa0…73c8

0x065c9d…c394

6 touches
3 conflicts

0xa4edc7b9…58e4

0x065c9d…c394

4 touches
1 conflict

0x1d7eacdc…3a91

0x065c9d…c394

3 touches
1 conflict

0x9faba861…17dc

0x065c9d…c394

3 touches
1 conflict

0xc53e02dc…c358

0x065c9d…c394

2 touches
0 conflicts

0xec114e85…ee8e

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

10 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity