← previous blocknext block →recent activity

Analyzing

Block #74,462,316

11 transactions · 11 stateful · 2026-05-14 04:13:31 UTC

Parallelism

73/100

Blocked

36%

Avg conflicts / tx

0.55

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,462,316  ·  11 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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xe54fabbb…6088

0x699abc…6a3b

6 touches
3 conflicts

0xd037c134…47b0

0x699abc…6a3b

6 touches
3 conflicts

0x335a161d…fe7f

0x000000…012a

6 touches
3 conflicts

0x1c389468…6b0e

0x34b655…2a6f

6 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0x7cee1be1…e770

0x34b655…2a6f

6 touches
3 conflicts

0xd0675a89…a9a3

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: 0x34b6552d…112a6f

3 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity