← previous blocknext block →recent activity

Analyzing

Block #74,409,564

28 transactions · 21 stateful · 2026-05-13 22:22:22 UTC

Parallelism

75/100

Blocked

62%

Avg conflicts / tx

1.39

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,409,564  ·  28 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xbec626ea…1b55

0xd32edf…ff58

13 touches
21 conflicts

0x00000000…0002

0x019883…2a9a

12 touches
15 conflicts

0x44ad89ba…cf83

0x0cc9b2…7777

12 touches
15 conflicts

0x99a3a7c1…1e2b

0x0cc9b2…7777

12 touches
15 conflicts

0x00000000…0000

0x019883…2a9a

12 touches
15 conflicts

0xa10c86f8…4b74

0x3bd359…433a

12 touches
15 conflicts

0xa472d565…9fe4

0x3bd359…433a

12 touches
15 conflicts

0x00000000…0000

0x116e7d…d8f1

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: 0xd32edf66…9fff58

21 conflicts on slot 0xbec626ea38…701b55

← previous block·next block →recent activity