← previous blocknext block →recent activity

Analyzing

Block #75,599,180

38 transactions · 29 stateful · 2026-05-19 10:57:40 UTC

Parallelism

74/100

Blocked

62%

Avg conflicts / tx

1.45

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #75,599,180  ·  38 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0x5ff227fb…bc89

0xd32edf…ff58

17 touches
36 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

10 touches
10 conflicts

0xcb45d9d6…cb82

0x1b6862…e19c

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0x00000000…0012

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…001a

0x1b6862…e19c

10 touches
10 conflicts

0x8a2f9a36…fb4a

0xfa32f9…f3f0

6 touches
3 conflicts

0x15698ac9…2a46

0x34b655…2a6f

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 0x5ff227fbe9…fbbc89

← previous block·next block →recent activity