← previous blocknext block →recent activity

Analyzing

Block #74,452,481

42 transactions · 28 stateful · 2026-05-14 03:08:00 UTC

Parallelism

79/100

Blocked

64%

Avg conflicts / tx

1.57

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #74,452,481  ·  42 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0xd1b33d40…149a

0xd32edf…ff58

17 touches
36 conflicts

0x00000000…0013

0x1b6862…e19c

14 touches
21 conflicts

0x00000000…0015

0x1b6862…e19c

14 touches
21 conflicts

0x928d6b23…5370

0x1b6862…e19c

14 touches
21 conflicts

0x1c389468…6b0e

0x34b655…2a6f

12 touches
15 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

12 touches
15 conflicts

0x00000000…0012

0x1b6862…e19c

12 touches
15 conflicts

0x00000000…001b

0x1b6862…e19c

12 touches
15 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 0xd1b33d400c…6d149a

← previous block·next block →recent activity