← previous blocknext block →recent activity

Analyzing

Block #73,651,267

19 transactions · 11 stateful · 2026-05-10 09:59:41 UTC

Parallelism

74/100

Blocked

36%

Avg conflicts / tx

0.26

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,651,267  ·  19 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

0x7f81fb82…633e

0x065c9d…c394

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x44adc290…2843

0xd32edf…ff58

3 touches
1 conflict

0x5609e871…a7e5

0x065c9d…c394

2 touches
0 conflicts

0xe2d3cc90…584f

0x065c9d…c394

2 touches
0 conflicts

0x09000000…0001

0x000000…1000

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 0x7f81fb82c1…ec633e

← previous block·next block →recent activity