← previous blocknext block →recent activity

Analyzing

Block #73,979,953

16 transactions · 12 stateful · 2026-05-11 22:42:25 UTC

Parallelism

81/100

Blocked

25%

Avg conflicts / tx

0.25

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,979,953  ·  16 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

0xf537eaa0…73c8

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x30276c1c…47b4

0x2a68ba…90c5

4 touches
1 conflict

0xa15427f6…d932

0x34b655…2a6f

4 touches
1 conflict

0x4aee0d7d…28b7

0x065c9d…c394

3 touches
1 conflict

0xdbbbc8fd…6f8d

0x065c9d…c394

2 touches
1 conflict

0x0bc84f1e…57fa

0x065c9d…c394

2 touches
1 conflict

0x99f666e3…b2a2

0x3bd359…433a

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

3 conflicts on slot 0xf537eaa0c6…3873c8

← previous block·next block →recent activity