← previous blocknext block →recent activity

Analyzing

Block #75,196,648

32 transactions · 27 stateful · 2026-05-17 14:00:58 UTC

Parallelism

75/100

Blocked

56%

Avg conflicts / tx

1.22

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #75,196,648  ·  32 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

0xd9f18d9a…141d

0x1b6862…e19c

12 touches
15 conflicts

0xcb45d9d6…cb82

0x1b6862…e19c

12 touches
15 conflicts

0x00000000…001a

0x1b6862…e19c

12 touches
15 conflicts

0x00000000…0012

0x1b6862…e19c

12 touches
15 conflicts

0x5180ed20…f17a

0xd32edf…ff58

11 touches
15 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

10 touches
10 conflicts

0x6af306bb…2e81

0x3bd359…433a

8 touches
6 conflicts

0xf91b744e…9117

0x754704…b603

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: 0x1b68626d…2de19c

15 conflicts on slot 0xd9f18d9a4a…7f141d

← previous block·next block →recent activity