← previous blocknext block →recent activity

Analyzing

Block #73,663,967

27 transactions · 21 stateful · 2026-05-10 11:25:16 UTC

Parallelism

74/100

Blocked

43%

Avg conflicts / tx

0.59

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #73,663,967  ·  27 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

0x897a5d74…bc28

0xd32edf…ff58

7 touches
6 conflicts

0x00000000…001c

0x1b6862…e19c

6 touches
3 conflicts

0xcb45d9d6…cb84

0x1b6862…e19c

6 touches
3 conflicts

0x7f81fb82…633e

0x065c9d…c394

6 touches
3 conflicts

0x17606ba6…1b6e

0x754704…b603

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x99f666e3…b2a2

0x3bd359…433a

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

6 conflicts on slot 0x897a5d74d4…9ebc28

← previous block·next block →recent activity