← previous blocknext block →recent activity

Analyzing

Block #74,406,610

46 transactions · 32 stateful · 2026-05-13 22:02:42 UTC

Parallelism

78/100

Blocked

78%

Avg conflicts / tx

1.76

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #74,406,610  ·  46 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

0xf5dc57ff…5d38

0xd32edf…ff58

17 touches
36 conflicts

0x00000000…0013

0x1b6862…e19c

16 touches
28 conflicts

0x00000000…0015

0x1b6862…e19c

16 touches
28 conflicts

0x00000000…001b

0x1b6862…e19c

16 touches
28 conflicts

0x00000000…002b

0x1b6862…e19c

16 touches
28 conflicts

0xb89c7e78…0bef

0x1b6862…e19c

16 touches
28 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

16 touches
28 conflicts

0x00000000…0012

0x1b6862…e19c

16 touches
28 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 0xf5dc57ffcf…7c5d38

← previous block·next block →recent activity