Block #73,668,936

← previous blocknext block →recent activity

Analyzing

Block #73,668,936

26 transactions · 23 stateful · 2026-05-10 11:58:52 UTC

Parallelism

69/100

Blocked

57%

Avg conflicts / tx

1.65

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #73,668,936  ·  26 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

0x08a5fb27…3a2f

0xd32edf…ff58

13 touches
21 conflicts

0x529acb6a…fcc6

0x065c9d…c394

12 touches
15 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x0ac31945…2c72

0x065c9d…c394

8 touches
6 conflicts

0xf58eca50…59fa

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

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

21 conflicts on slot 0x08a5fb27d6…613a2f

← previous block·next block →recent activity