← previous blocknext block →recent activity

Analyzing

Block #75,478,232

54 transactions · 25 stateful · 2026-05-18 21:23:08 UTC

Parallelism

80/100

Blocked

76%

Avg conflicts / tx

1.65

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #75,478,232  ·  54 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0xa650b3f2…3f56

0xd32edf…ff58

21 touches
55 conflicts

0x0dbf9688…c6cf

0xd18b7e…414b

12 touches
15 conflicts

0x17606ba6…1b6e

0x754704…b603

12 touches
15 conflicts

0x4039b31f…0f4a

0x754704…b603

8 touches
6 conflicts

0xe75ce681…ba5f

0x188d58…ea8e

8 touches
6 conflicts

0x00000000…0005

0x5afd3e…7620

8 touches
6 conflicts

0x5d82c9b5…004c

0x3bd359…433a

8 touches
6 conflicts

0x00000000…0004

0x5afd3e…7620

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

55 conflicts on slot 0xa650b3f241…733f56

← previous block·next block →recent activity