Block #73,744,481

← previous blocknext block →recent activity

Analyzing

Block #73,744,481

25 transactions · 22 stateful · 2026-05-10 20:28:38 UTC

Parallelism

76/100

Blocked

55%

Avg conflicts / tx

1.32

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,744,481  ·  25 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x529acb6a…fcc6

0x065c9d…c394

10 touches
10 conflicts

0x00000000…003d

0x065c9d…c394

10 touches
10 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

10 touches
10 conflicts

0x046a928e…0012

0x2a68ba…90c5

10 touches
10 conflicts

0x0ac31945…2c72

0x065c9d…c394

8 touches
6 conflicts

0xb378025c…30cf

0x34b655…2a6f

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0x908d4442…2c4b

0x34b655…2a6f

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: 0x065c9d28…a9c394

10 conflicts on slot 0x529acb6ad1…f0fcc6

← previous block·next block →recent activity