← previous blocknext block →recent activity

Analyzing

Block #75,262,727

14 transactions · 12 stateful · 2026-05-17 21:22:29 UTC

Parallelism

71/100

Blocked

50%

Avg conflicts / tx

0.57

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #75,262,727  ·  14 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x00000000…001c

0x1b6862…e19c

6 touches
3 conflicts

0x3e693216…fa0e

0x34b655…2a6f

6 touches
3 conflicts

0xcb45d9d6…cb84

0x1b6862…e19c

6 touches
3 conflicts

0xdd416f88…0448

0xd32edf…ff58

5 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

4 touches
1 conflict

0x908d4442…2c4b

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xe54a1f6f…18f2

0x34b655…2a6f

4 touches
1 conflict

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

3 conflicts on slot 0x0000000000…00001c

← previous block·next block →recent activity