← previous blocknext block →recent activity

Analyzing

Block #75,478,236

27 transactions · 13 stateful · 2026-05-18 21:23:09 UTC

Parallelism

78/100

Blocked

46%

Avg conflicts / tx

0.48

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #75,478,236  ·  27 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

0xc3d7b6bc…e506

0xd32edf…ff58

9 touches
10 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x2b093939…9083

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

4 touches
1 conflict

0x01e7b865…6e6d

0x188d58…ea8e

4 touches
1 conflict

0x01e7b865…6e6f

0x188d58…ea8e

4 touches
1 conflict

0xe75ce681…ba5f

0x188d58…ea8e

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: 0xd32edf66…9fff58

10 conflicts on slot 0xc3d7b6bc6e…72e506

← previous block·next block →recent activity