Block #73,336,356

← previous blocknext block →recent activity

Analyzing

Block #73,336,356

18 transactions · 16 stateful · 2026-05-08 23:02:26 UTC

Parallelism

61/100

Blocked

44%

Avg conflicts / tx

1.22

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #73,336,356  ·  18 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x6f08361d…bda6

0x065c9d…c394

14 touches
21 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

12 touches
15 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x979e5818…c903

0x065c9d…c394

6 touches
5 conflicts

0x1f8080e5…fadc

0x065c9d…c394

5 touches
3 conflicts

0x4e48a13b…545d

0x065c9d…c394

5 touches
3 conflicts

0xc53e02dc…c358

0x065c9d…c394

5 touches
3 conflicts

0xd821ae10…fe17

0xc8689a…ee79

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

21 conflicts on slot 0x6f08361da9…89bda6

← previous block·next block →recent activity