← previous blocknext block →recent activity

Analyzing

Block #74,923,378

34 transactions · 19 stateful · 2026-05-16 07:35:25 UTC

Parallelism

91/100

Blocked

37%

Avg conflicts / tx

0.26

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,923,378  ·  34 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x17606ba6…1b6e

0x754704…b603

6 touches
3 conflicts

0x4657667a…59b8

0xd32edf…ff58

5 touches
3 conflicts

0x00000000…0001

0x86dfd5…6a7d

4 touches
1 conflict

0x1d4c90ab…1ba7

0xb72e62…7777

4 touches
1 conflict

0x44ad89ba…cf83

0xb72e62…7777

4 touches
1 conflict

0x4aa4f53b…89a1

0x188d58…ea8e

4 touches
1 conflict

0x1686502b…a1d2

0x3bd359…433a

4 touches
1 conflict

0xa472d565…9fe4

0x3bd359…433a

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: 0x754704bc…afb603

3 conflicts on slot 0x17606ba612…ea1b6e

← previous block·next block →recent activity