← previous blocknext block →recent activity

Analyzing

Block #75,513,292

42 transactions · 23 stateful · 2026-05-19 01:23:39 UTC

Parallelism

83/100

Blocked

70%

Avg conflicts / tx

1.02

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #75,513,292  ·  42 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

0x43675f41…4151

0xd32edf…ff58

13 touches
21 conflicts

0x17606ba6…1b6e

0x754704…b603

8 touches
6 conflicts

0x01e7b865…6e6d

0x188d58…ea8e

8 touches
6 conflicts

0x99a21305…dffc

0x2a68ba…90c5

6 touches
3 conflicts

0x443a3e47…f4a4

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x5086c64a…28ba

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

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

21 conflicts on slot 0x43675f4136…f64151

← previous block·next block →recent activity