← previous blocknext block →recent activity

Analyzing

Block #73,705,283

7 transactions · 7 stateful · 2026-05-10 16:04:05 UTC

Parallelism

57/100

Blocked

29%

Avg conflicts / tx

0.43

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,705,283  ·  7 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

6 touches
3 conflicts

0x10e9656e…8815

0x065c9d…c394

6 touches
3 conflicts

0x6cc46942…768c

0x065c9d…c394

6 touches
3 conflicts

0x50997ada…364d

0x6c4bfa…a540

6 touches
3 conflicts

0xf0f673fd…37a7

0x6c4bfa…a540

6 touches
3 conflicts

0xed57bddf…1abf

0xc8689a…ee79

6 touches
3 conflicts

0x5d81c137…160f

0x065c9d…c394

4 touches
3 conflicts

0xae69c125…2379

0x2a68ba…90c5

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

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity