Block #74,033,820

← previous blocknext block →recent activity

Analyzing

Block #74,033,820

20 transactions · 16 stateful · 2026-05-12 04:42:39 UTC

Parallelism

70/100

Blocked

63%

Avg conflicts / tx

1.1

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,033,820  ·  20 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

0x7451b642…dc5c

0xd32edf…ff58

11 touches
15 conflicts

0x00000000…002b

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…001b

0x1b6862…e19c

6 touches
3 conflicts

0xd59f6ed1…03e7

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

15 conflicts on slot 0x7451b642d9…e4dc5c

← previous block·next block →recent activity