Block #73,333,852

← previous blocknext block →recent activity

Analyzing

Block #73,333,852

17 transactions · 15 stateful · 2026-05-08 22:45:50 UTC

Parallelism

65/100

Blocked

33%

Avg conflicts / tx

0.88

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,333,852  ·  17 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

0xf537eaa0…73c8

0x065c9d…c394

12 touches
15 conflicts

0x046a928e…0012

0x2a68ba…90c5

10 touches
10 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x1ecea97d…3ca9

0x065c9d…c394

2 touches
0 conflicts

0x8fa7a69c…8fd7

0x26af86…7777

2 touches
0 conflicts

0x536e2740…61ac

0x3bd359…433a

2 touches
0 conflicts

0x99f666e3…b2a2

0x3bd359…433a

2 touches
0 conflicts

0xa472d565…9fe4

0x3bd359…433a

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

15 conflicts on slot 0xf537eaa0c6…3873c8

← previous block·next block →recent activity