Block #73,338,112

← previous blocknext block →recent activity

Analyzing

Block #73,338,112

14 transactions · 11 stateful · 2026-05-08 23:14:09 UTC

Parallelism

64/100

Blocked

36%

Avg conflicts / tx

0.5

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,338,112  ·  14 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

0xbd7e37a9…9eb5

0x065c9d…c394

6 touches
3 conflicts

0xd821ae10…fe17

0xc8689a…ee79

4 touches
1 conflict

0x0b390c61…dc07

0x065c9d…c394

4 touches
1 conflict

0x1a4b4152…0a08

0xaba216…a862

4 touches
1 conflict

0x50997ada…364d

0xaba216…a862

4 touches
1 conflict

0xc5564f8e…f4bf

0xaba216…a862

4 touches
1 conflict

0xf0f673fd…37a7

0xaba216…a862

4 touches
1 conflict

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