Block #73,660,513

← previous blocknext block →recent activity

Analyzing

Block #73,660,513

21 transactions · 19 stateful · 2026-05-10 11:01:57 UTC

Parallelism

67/100

Blocked

53%

Avg conflicts / tx

1.05

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #73,660,513  ·  21 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xf2f76ab3…623e

0x2a68ba…90c5

10 touches
10 conflicts

0xc91ce165…fdae

0xd32edf…ff58

7 touches
6 conflicts

0xb159af88…a9e7

0x065c9d…c394

6 touches
3 conflicts

0x7f81fb82…633e

0x065c9d…c394

6 touches
3 conflicts

0x00000000…001c

0x1b6862…e19c

4 touches
1 conflict

0x00000000…002c

0x1b6862…e19c

4 touches
1 conflict

0xba5743c7…21c3

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

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: 0x2a68ba18…8e90c5

10 conflicts on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity