← previous blocknext block →recent activity

Analyzing

Block #75,676,099

20 transactions · 16 stateful · 2026-05-19 19:32:02 UTC

Parallelism

70/100

Blocked

31%

Avg conflicts / tx

0.75

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #75,676,099  ·  20 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xa36a973a…a245

0xd32edf…ff58

11 touches
15 conflicts

0xcb45d9d6…cb84

0x1b6862…e19c

8 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0012

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…001c

0x1b6862…e19c

8 touches
6 conflicts

0x455b104f…3960

0xea1b8e…c5ec

2 touches
0 conflicts

0xa8abcc19…3d83

0xea1b8e…c5ec

2 touches
0 conflicts

0xaa2f6971…c549

0xea1b8e…c5ec

2 touches
0 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

15 conflicts on slot 0xa36a973a58…0fa245

← previous block·next block →recent activity