← previous blocknext block →recent activity

Analyzing

Block #74,613,081

38 transactions · 25 stateful · 2026-05-14 21:04:31 UTC

Parallelism

76/100

Blocked

40%

Avg conflicts / tx

0.76

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #74,613,081  ·  38 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

0x1635d45c…fe55

0xd32edf…ff58

13 touches
21 conflicts

0xd53220ed…473b

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0x92d610a6…9a40

0x2a68ba…90c5

8 touches
6 conflicts

0x726f035a…3c59

0x065c9d…c394

7 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

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

21 conflicts on slot 0x1635d45cf1…87fe55

← previous block·next block →recent activity