← previous blocknext block →recent activity

Analyzing

Block #74,920,511

29 transactions · 25 stateful · 2026-05-16 07:16:12 UTC

Parallelism

79/100

Blocked

52%

Avg conflicts / tx

1.07

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,920,511  ·  29 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x02c05d27…ebf8

0xd32edf…ff58

11 touches
15 conflicts

0xea02471d…1542

0x34b655…2a6f

8 touches
6 conflicts

0xb9868b52…c77f

0x34b655…2a6f

8 touches
6 conflicts

0x0380ead4…3a27

0x34b655…2a6f

6 touches
3 conflicts

0xfcb7b8b2…ebb3

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0x8db1e0f2…2fcf

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

15 conflicts on slot 0x02c05d2739…47ebf8

← previous block·next block →recent activity