← previous blocknext block →recent activity

Analyzing

Block #75,512,642

34 transactions · 25 stateful · 2026-05-19 01:19:14 UTC

Parallelism

79/100

Blocked

48%

Avg conflicts / tx

0.79

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #75,512,642  ·  34 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x15698ac9…2a46

0x34b655…2a6f

12 touches
15 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

12 touches
15 conflicts

0xea02471d…1542

0x34b655…2a6f

8 touches
6 conflicts

0xded5ec0c…f0fc

0x34b655…2a6f

8 touches
6 conflicts

0x9144e3a9…3d6e

0x34b655…2a6f

6 touches
3 conflicts

0xb7b9f693…3387

0xd32edf…ff58

5 touches
3 conflicts

0x00000000…0029

0x1b6862…e19c

4 touches
1 conflict

0xc3483764…f297

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

15 conflicts on slot 0x15698ac9db…df2a46

← previous block·next block →recent activity