Block #73,204,603

← previous blocknext block →recent activity

Analyzing

Block #73,204,603

7 transactions · 6 stateful · 2026-05-08 08:25:58 UTC

Parallelism

71/100

Blocked

17%

Avg conflicts / tx

0.29

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,204,603  ·  7 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x7f189cf6…afab

0x065c9d…c394

4 touches
1 conflict

0x7e3bdb67…221d

0x065c9d…c394

2 touches
0 conflicts

0x818e18ff…1b38

0x065c9d…c394

2 touches
0 conflicts

0xbd2fca5c…7157

0x065c9d…c394

2 touches
0 conflicts

0xc5289189…89e5

0x065c9d…c394

2 touches
0 conflicts

0xce7bfe5e…5e58

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

1 conflict on slot 0x046a928e85…e50012

← previous block·next block →recent activity