← previous blocknext block →recent activity

Analyzing

Block #75,096,304

18 transactions · 17 stateful · 2026-05-17 02:51:03 UTC

Parallelism

72/100

Blocked

59%

Avg conflicts / tx

1.33

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #75,096,304  ·  18 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x60f7fbaf…bd58

0x34b655…2a6f

10 touches
10 conflicts

0x11f25e19…8bb1

0x34b655…2a6f

8 touches
6 conflicts

0x6a516ecd…8e0d

0xd32edf…ff58

7 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0xda6b535e…6d67

0x1b6862…e19c

6 touches
3 conflicts

0xfcb7b8b2…ebb3

0x065c9d…c394

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x9859453c…c30f

0x065c9d…c394

5 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: 0x34b6552d…112a6f

10 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity