← previous blocknext block →recent activity

Analyzing

Block #75,732,660

29 transactions · 25 stateful · 2026-05-20 01:48:17 UTC

Parallelism

83/100

Blocked

52%

Avg conflicts / tx

0.97

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #75,732,660  ·  29 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x6ff6f462…bc63

0xd32edf…ff58

9 touches
10 conflicts

0x422d5490…52d9

0x34b655…2a6f

8 touches
6 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…0012

0x1b6862…e19c

8 touches
6 conflicts

0xcb45d9d6…cb85

0x1b6862…e19c

8 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…001d

0x1b6862…e19c

8 touches
6 conflicts

0x0d622e34…0000

0x681e90…ae09

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

10 conflicts on slot 0x6ff6f4626b…95bc63

← previous block·next block →recent activity