← previous blocknext block →recent activity

Analyzing

Block #75,340,187

22 transactions · 17 stateful · 2026-05-18 06:00:59 UTC

Parallelism

64/100

Blocked

53%

Avg conflicts / tx

1.32

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #75,340,187  ·  22 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0xa51a54ba…9c72

0xd32edf…ff58

13 touches
21 conflicts

0x00000000…002d

0x1b6862…e19c

6 touches
3 conflicts

0x9885a25f…292b

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0x92d610a6…9a40

0x2a68ba…90c5

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…001d

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

21 conflicts on slot 0xa51a54bad6…929c72

← previous block·next block →recent activity