← previous blocknext block →recent activity

Analyzing

Block #73,639,253

32 transactions · 22 stateful · 2026-05-10 08:38:50 UTC

Parallelism

84/100

Blocked

36%

Avg conflicts / tx

0.5

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,639,253  ·  32 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

0xdde0ade6…d303

0xd32edf…ff58

9 touches
10 conflicts

0xea02471d…1539

0x34b655…2a6f

4 touches
1 conflict

0x12309510…0ac2

0x000000…012a

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xb3f5304f…1d16

0x065c9d…c394

4 touches
1 conflict

0xc9e97522…3519

0x2a68ba…90c5

4 touches
1 conflict

0x6cd5e1ef…c148

0x34b655…2a6f

4 touches
1 conflict

0xb81d3ee7…3947

0x34b655…2a6f

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: 0xd32edf66…9fff58

10 conflicts on slot 0xdde0ade670…2ad303

← previous block·next block →recent activity