← previous blocknext block →recent activity

Analyzing

Block #73,048,512

12 transactions · 11 stateful · 2026-05-07 15:07:28 UTC

Parallelism

58/100

Blocked

45%

Avg conflicts / tx

0.92

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,048,512  ·  12 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

0x8e66da19…66b6

0x065c9d…c394

10 touches
10 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x4e5ebbf7…ae70

0xc8689a…ee79

4 touches
1 conflict

0x3e4b8d9f…b8a7

0x6ca43f…c331

4 touches
1 conflict

0xc5564f8e…f4bf

0x6ca43f…c331

4 touches
1 conflict

0xeb27550d…6028

0x6ca43f…c331

4 touches
1 conflict

0xf0f673fd…37a7

0x6ca43f…c331

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

10 conflicts on slot 0x8e66da1932…c966b6

← previous block·next block →recent activity