Block #73,374,950

← previous blocknext block →recent activity

Analyzing

Block #73,374,950

36 transactions · 32 stateful · 2026-05-09 03:19:13 UTC

Parallelism

64/100

Blocked

50%

Avg conflicts / tx

1.42

Longest chain

13 deep

Execution timeline

did this block parallelize well?

view

block #73,374,950  ·  36 txs across 13 waves  ·  depth 13
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

wave w12

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

0x00000000…003d

0x065c9d…c394

14 touches
21 conflicts

0x4d87512b…897c

0x065c9d…c394

12 touches
15 conflicts

0xc906f55e…8dc1

0xd32edf…ff58

11 touches
15 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

10 touches
10 conflicts

0xa7fe0d97…ae1c

0x2a68ba…90c5

8 touches
6 conflicts

0x22e295f5…1bef

0x065c9d…c394

8 touches
6 conflicts

0x71b76c32…a6ab

0x065c9d…c394

8 touches
6 conflicts

0xa1087a5c…66c4

0x754704…b603

8 touches
6 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

21 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity