← previous blocknext block →recent activity

Analyzing

Block #74,360,672

28 transactions · 21 stateful · 2026-05-13 16:56:50 UTC

Parallelism

64/100

Blocked

67%

Avg conflicts / tx

1.79

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #74,360,672  ·  28 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0x2c9ef79e…bf29

0xd32edf…ff58

17 touches
36 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x47b807a2…3307

0x065c9d…c394

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x41755291…977f

0x065c9d…c394

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x928d6b23…536f

0x1b6862…e19c

6 touches
3 conflicts

0x765c236f…ff45

0x2a68ba…90c5

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

36 conflicts on slot 0x2c9ef79e52…71bf29

← previous block·next block →recent activity