Block #73,638,709

← previous blocknext block →recent activity

Analyzing

Block #73,638,709

19 transactions · 17 stateful · 2026-05-10 08:35:09 UTC

Parallelism

58/100

Blocked

53%

Avg conflicts / tx

1.58

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #73,638,709  ·  19 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0xcb110f99…c31f

0xd32edf…ff58

15 touches
28 conflicts

0x22e295f5…1bef

0x065c9d…c394

4 touches
1 conflict

0xae69c125…2379

0x2a68ba…90c5

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0xdca15959…4407

0x065c9d…c394

2 touches
0 conflicts

0x01e7b865…6e6d

0x188d58…ea8e

2 touches
0 conflicts

0x01e7b865…6e6e

0x188d58…ea8e

2 touches
0 conflicts

0x00000000…0012

0x1b6862…e19c

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

28 conflicts on slot 0xcb110f994b…68c31f

← previous block·next block →recent activity