← previous blocknext block →recent activity

Analyzing

Block #74,730,984

46 transactions · 30 stateful · 2026-05-15 10:11:12 UTC

Parallelism

78/100

Blocked

63%

Avg conflicts / tx

1.26

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #74,730,984  ·  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

0x1b78b0a9…e3ed

0xd32edf…ff58

15 touches
28 conflicts

0x00000000…0015

0x1b6862…e19c

10 touches
10 conflicts

0x92d610a6…9a40

0x2a68ba…90c5

10 touches
10 conflicts

0x083a8763…5a79

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…0013

0x1b6862…e19c

10 touches
10 conflicts

0x12309510…0ac2

0x000000…012a

8 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

8 touches
6 conflicts

0xf3d7a307…4d63

0x065c9d…c394

8 touches
6 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

28 conflicts on slot 0x1b78b0a9c1…c7e3ed

← previous block·next block →recent activity