← previous blocknext block →recent activity

Analyzing

Block #73,650,259

14 transactions · 11 stateful · 2026-05-10 09:52:57 UTC

Parallelism

71/100

Blocked

27%

Avg conflicts / tx

0.43

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,650,259  ·  14 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xb159af88…a9e7

0x065c9d…c394

8 touches
6 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x15d4cb6f…bed3

0x065c9d…c394

2 touches
0 conflicts

0x5edff3c4…8805

0x065c9d…c394

2 touches
0 conflicts

0x97d510f6…1349

0x065c9d…c394

2 touches
0 conflicts

0xa0e2b408…be3f

0x065c9d…c394

2 touches
0 conflicts

0xdbd474a9…3238

0x065c9d…c394

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

6 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity