← previous blocknext block →recent activity

Analyzing

Block #74,920,282

28 transactions · 22 stateful · 2026-05-16 07:14:39 UTC

Parallelism

79/100

Blocked

41%

Avg conflicts / tx

0.54

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,920,282  ·  28 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x7bff2b89…905c

0xd32edf…ff58

7 touches
6 conflicts

0x2bbc0cfb…c2c0

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…001d

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…002d

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

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

6 conflicts on slot 0x7bff2b895b…0f905c

← previous block·next block →recent activity