← previous blocknext block →recent activity

Analyzing

Block #75,478,692

35 transactions · 17 stateful · 2026-05-18 21:26:14 UTC

Parallelism

74/100

Blocked

76%

Avg conflicts / tx

1.34

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #75,478,692  ·  35 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

0x3115d102…2886

0xd32edf…ff58

17 touches
36 conflicts

0xe75ce681…ba5f

0x188d58…ea8e

8 touches
6 conflicts

0x0dbf9688…c6cf

0xd18b7e…414b

8 touches
6 conflicts

0x17606ba6…1b6e

0x754704…b603

8 touches
6 conflicts

0x00000000…0018

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0028

0x1b6862…e19c

6 touches
3 conflicts

0x2b093939…9083

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

36 conflicts on slot 0x3115d1021f…662886

← previous block·next block →recent activity