← previous blocknext block →recent activity

Analyzing

Block #75,478,942

31 transactions · 19 stateful · 2026-05-18 21:27:56 UTC

Parallelism

71/100

Blocked

63%

Avg conflicts / tx

1.42

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #75,478,942  ·  31 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0x083c17a2…c760

0xd32edf…ff58

17 touches
36 conflicts

0x846f2172…fd54

0x0555e3…2b9c

8 touches
6 conflicts

0x46cb45de…a566

0x188d58…ea8e

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x14d1bf0e…e099

0x1b6862…e19c

6 touches
3 conflicts

0x51ca3051…0972

0x3bd359…433a

6 touches
3 conflicts

0x00000000…0000

0x614b85…a284

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

36 conflicts on slot 0x083c17a228…93c760

← previous block·next block →recent activity