← previous blocknext block →recent activity

Analyzing

Block #75,540,293

19 transactions · 12 stateful · 2026-05-19 04:25:35 UTC

Parallelism

84/100

Blocked

33%

Avg conflicts / tx

0.26

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #75,540,293  ·  19 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xdc2eede0…0d77

0xd32edf…ff58

5 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x90a7fc1a…56c3

0x065c9d…c394

3 touches
1 conflict

0x60b24061…7c23

0x188d58…ea8e

2 touches
0 conflicts

0x60b24061…7c24

0x188d58…ea8e

2 touches
0 conflicts

0xe75ce681…ba5f

0x188d58…ea8e

2 touches
0 conflicts

0xe75ce681…ba61

0x188d58…ea8e

2 touches
0 conflicts

0x05a30e31…2713

0x3bd359…433a

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

3 conflicts on slot 0xdc2eede04b…a30d77

← previous block·next block →recent activity