← previous blocknext block →recent activity

Analyzing

Block #73,014,572

21 transactions · 12 stateful · 2026-05-07 11:21:31 UTC

Parallelism

76/100

Blocked

42%

Avg conflicts / tx

0.76

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,014,572  ·  21 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

0xd6c5e267…6582

0x065c9d…c394

9 touches
10 conflicts

0xa1087a5c…66c4

0x754704…b603

8 touches
6 conflicts

0xe09eda07…8dda

0x2a68ba…90c5

8 touches
6 conflicts

0x30030c00…cc72

0xd32edf…ff58

5 touches
3 conflicts

0x00000000…0004

0x094452…0a09

4 touches
1 conflict

0x62e20208…be65

0x0555e3…2b9c

4 touches
1 conflict

0x846f2172…fd54

0x0555e3…2b9c

4 touches
1 conflict

0x00000000…0000

0x094452…0a09

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 0xd6c5e2678c…376582

← previous block·next block →recent activity