Block #73,649,171

← previous blocknext block →recent activity

Analyzing

Block #73,649,171

19 transactions · 16 stateful · 2026-05-10 09:45:37 UTC

Parallelism

63/100

Blocked

38%

Avg conflicts / tx

0.63

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #73,649,171  ·  19 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

0x7f81fb82…633e

0x065c9d…c394

8 touches
6 conflicts

0xe67218c2…ab26

0xd32edf…ff58

7 touches
6 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0xcb45d9d6…cb83

0x1b6862…e19c

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x00000000…001b

0x1b6862…e19c

4 touches
1 conflict

0x3517e4a5…859c

0x065c9d…c394

3 touches
1 conflict

0x00c2170a…a771

0x065c9d…c394

3 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

6 conflicts on slot 0x7f81fb82c1…ec633e

← previous block·next block →recent activity