Block #73,348,628

← previous blocknext block →recent activity

Analyzing

Block #73,348,628

19 transactions · 12 stateful · 2026-05-09 00:24:06 UTC

Parallelism

74/100

Blocked

42%

Avg conflicts / tx

0.42

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,348,628  ·  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

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x4d87512b…897c

0x065c9d…c394

8 touches
6 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0xd4c034e4…9429

0xd32edf…ff58

3 touches
1 conflict

0x9e6d9d4f…25ca

0x065c9d…c394

2 touches
0 conflicts

0xa2b6fcc3…0048

0x065c9d…c394

2 touches
0 conflicts

0xe21c3393…ee60

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

6 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity