← previous blocknext block →recent activity

Analyzing

Block #74,504,974

11 transactions · 8 stateful · 2026-05-14 08:57:36 UTC

Parallelism

82/100

Blocked

38%

Avg conflicts / tx

0.27

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,504,974  ·  11 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x0872abbe…9c39

0x2a68ba…90c5

4 touches
1 conflict

0x5c8c6ab6…dc36

0x065c9d…c394

4 touches
1 conflict

0xb5963e67…31a4

0xd32edf…ff58

3 touches
1 conflict

0x68c59869…9e39

0x065c9d…c394

2 touches
0 conflicts

0x00000000…0007

0x09f880…ede0

2 touches
0 conflicts

0x00000000…000a

0x09f880…ede0

2 touches
0 conflicts

0x438cf5f6…f077

0x2a68ba…90c5

2 touches
0 conflicts

0x765c236f…ff45

0x2a68ba…90c5

2 touches
0 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: 0x2a68ba18…8e90c5

1 conflict on slot 0x0872abbeb4…d69c39

← previous block·next block →recent activity