← previous blocknext block →recent activity

Analyzing

Block #75,501,972

26 transactions · 15 stateful · 2026-05-19 00:06:02 UTC

Parallelism

73/100

Blocked

53%

Avg conflicts / tx

0.88

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #75,501,972  ·  26 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

0xa2380a54…d46a

0xd32edf…ff58

13 touches
21 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0xa92c8763…6d7f

0x34b655…2a6f

4 touches
1 conflict

0x5f77d607…2c84

0x065c9d…c394

2 touches
0 conflicts

0x6e7c3322…c01c

0x065c9d…c394

2 touches
0 conflicts

0xce729afd…8473

0x065c9d…c394

2 touches
0 conflicts

0x01e7b865…6e6d

0x188d58…ea8e

2 touches
0 conflicts

0x01e7b865…6e6e

0x188d58…ea8e

2 touches
0 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 0xa2380a5448…f7d46a

← previous block·next block →recent activity