← previous blocknext block →recent activity

Analyzing

Block #75,129,423

13 transactions · 13 stateful · 2026-05-17 06:32:08 UTC

Parallelism

62/100

Blocked

54%

Avg conflicts / tx

1.08

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #75,129,423  ·  13 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

0xda27ab6f…0cf1

0xd32edf…ff58

9 touches
10 conflicts

0x00000000…0029

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0012

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0019

0x1b6862…e19c

8 touches
6 conflicts

0x6b1259e6…4e0e

0x1b6862…e19c

8 touches
6 conflicts

0xd9f18d9a…141d

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: 0xd32edf66…9fff58

10 conflicts on slot 0xda27ab6f70…4f0cf1

← previous block·next block →recent activity