← previous blocknext block →recent activity

Analyzing

Block #75,513,296

51 transactions · 32 stateful · 2026-05-19 01:23:41 UTC

Parallelism

78/100

Blocked

63%

Avg conflicts / tx

1.39

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #75,513,296  ·  51 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

0x08cccf1a…979c

0xd32edf…ff58

21 touches
55 conflicts

0x00000000…0002

0x019883…2a9a

6 touches
3 conflicts

0x44ad89ba…cf83

0x0cc9b2…7777

6 touches
3 conflicts

0x99a3a7c1…1e2b

0x0cc9b2…7777

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0xa10c86f8…4b74

0x3bd359…433a

6 touches
3 conflicts

0xa472d565…9fe4

0x3bd359…433a

6 touches
3 conflicts

0x17606ba6…1b6e

0x754704…b603

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

55 conflicts on slot 0x08cccf1afe…f1979c

← previous block·next block →recent activity