← previous blocknext block →recent activity

Analyzing

Block #75,309,643

23 transactions · 19 stateful · 2026-05-18 02:36:43 UTC

Parallelism

83/100

Blocked

37%

Avg conflicts / tx

0.48

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #75,309,643  ·  23 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

0x92d610a6…9a40

0x2a68ba…90c5

6 touches
3 conflicts

0x33018431…8f5c

0x188d58…ea8e

6 touches
3 conflicts

0x17606ba6…1b6e

0x754704…b603

6 touches
3 conflicts

0x443a3e47…f4a4

0x065c9d…c394

6 touches
3 conflicts

0x12309510…0ac2

0x000000…012a

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

4 touches
1 conflict

0x00000000…001d

0x1b6862…e19c

4 touches
1 conflict

0xcb45d9d6…cb85

0x1b6862…e19c

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: 0x2a68ba18…8e90c5

3 conflicts on slot 0x92d610a6f9…379a40

← previous block·next block →recent activity