← previous blocknext block →recent activity

Analyzing

Block #73,869,213

22 transactions · 19 stateful · 2026-05-11 10:24:37 UTC

Parallelism

77/100

Blocked

63%

Avg conflicts / tx

1.36

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,869,213  ·  22 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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…0007

0x1414f3…5137

10 touches
10 conflicts

0x5de96bd3…c60c

0x34b655…2a6f

10 touches
10 conflicts

0x00000000…003d

0x065c9d…c394

10 touches
10 conflicts

0x23951077…539b

0x34b655…2a6f

8 touches
6 conflicts

0x8834c319…ef73

0x34b655…2a6f

8 touches
6 conflicts

0xf853eb8e…4027

0x34b655…2a6f

8 touches
6 conflicts

0x5d70606a…1d53

0x34b655…2a6f

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

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: 0x1414f3ba…045137

10 conflicts on slot 0x0000000000…000007

← previous block·next block →recent activity