Block #73,338,375

← previous blocknext block →recent activity

Analyzing

Block #73,338,375

40 transactions · 30 stateful · 2026-05-08 23:15:53 UTC

Parallelism

53/100

Blocked

63%

Avg conflicts / tx

3.55

Longest chain

19 deep

Execution timeline

did this block parallelize well?

view

block #73,338,375  ·  40 txs across 19 waves  ·  depth 19
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

wave w13

wave w14

wave w15

wave w16

wave w17

wave w18

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

0x66b5f2f5…7b03

0xd32edf…ff58

33 touches
136 conflicts

0x00000000…0013

0x1b6862…e19c

14 touches
21 conflicts

0xd25997d0…a688

0x1b6862…e19c

14 touches
21 conflicts

0x00000000…0015

0x1b6862…e19c

14 touches
21 conflicts

0x00000000…001d

0x1b6862…e19c

12 touches
15 conflicts

0x00000000…0012

0x1b6862…e19c

12 touches
15 conflicts

0x00000000…002d

0x1b6862…e19c

12 touches
15 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

12 touches
15 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

136 conflicts on slot 0x66b5f2f528…7a7b03

← previous block·next block →recent activity