← previous blocknext block →recent activity

Analyzing

Block #75,679,489

23 transactions · 14 stateful · 2026-05-19 19:54:35 UTC

Parallelism

83/100

Blocked

43%

Avg conflicts / tx

0.39

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #75,679,489  ·  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

0xcc4f1f14…aa5f

0x065c9d…c394

6 touches
3 conflicts

0x5378c63b…d238

0xd32edf…ff58

5 touches
3 conflicts

0x00000000…002c

0x1b6862…e19c

4 touches
1 conflict

0x0e5f9bfa…6d5a

0x34b655…2a6f

4 touches
1 conflict

0x4546ebad…b908

0x34b655…2a6f

4 touches
1 conflict

0x74e485b1…d380

0x34b655…2a6f

4 touches
1 conflict

0xac206e47…ef7d

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

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: 0x065c9d28…a9c394

3 conflicts on slot 0xcc4f1f1446…7caa5f

← previous block·next block →recent activity