← previous blocknext block →recent activity

Analyzing

Block #73,393,512

14 transactions · 12 stateful · 2026-05-09 05:22:41 UTC

Parallelism

64/100

Blocked

33%

Avg conflicts / tx

0.71

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

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

0x4d87512b…897c

0x065c9d…c394

10 touches
10 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x22e295f5…1bef

0x065c9d…c394

4 touches
1 conflict

0x33aee544…68dd

0x065c9d…c394

4 touches
1 conflict

0x3cd59e91…7f4d

0x065c9d…c394

4 touches
1 conflict

0x4e766fad…79a6

0xc8689a…ee79

4 touches
1 conflict

0x0f2a0e87…dfd7

0x065c9d…c394

4 touches
1 conflict

0x2e2214a9…fe0d

0x8e764f…e322

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 0x4d87512b00…43897c

← previous block·next block →recent activity