← previous blocknext block →recent activity

Analyzing

Block #75,679,559

19 transactions · 16 stateful · 2026-05-19 19:55:04 UTC

Parallelism

68/100

Blocked

38%

Avg conflicts / tx

0.68

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #75,679,559  ·  19 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

0xec85b41e…7c94

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…0013

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…0015

0x1b6862…e19c

10 touches
10 conflicts

0x137a5e35…eda9

0xd32edf…ff58

9 touches
10 conflicts

0x00000000…002c

0x1b6862…e19c

8 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…001c

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0012

0x1b6862…e19c

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: 0x1b68626d…2de19c

10 conflicts on slot 0xec85b41e7d…047c94

← previous block·next block →recent activity