← previous blocknext block →recent activity

Analyzing

Block #75,502,255

40 transactions · 30 stateful · 2026-05-19 00:07:57 UTC

Parallelism

80/100

Blocked

50%

Avg conflicts / tx

0.88

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #75,502,255  ·  40 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

0x46137f6a…5743

0xd32edf…ff58

13 touches
21 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…0018

0x1b6862…e19c

10 touches
10 conflicts

0xcb45d9d6…cb80

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…0012

0x1b6862…e19c

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xf853eb8e…4027

0x34b655…2a6f

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

21 conflicts on slot 0x46137f6ac9…755743

← previous block·next block →recent activity