← previous blocknext block →recent activity

Analyzing

Block #75,093,217

25 transactions · 18 stateful · 2026-05-17 02:30:32 UTC

Parallelism

76/100

Blocked

56%

Avg conflicts / tx

0.64

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #75,093,217  ·  25 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x348fda08…7e96

0x065c9d…c394

8 touches
6 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0xdfc403eb…5740

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xe19c499e…9ea7

0x065c9d…c394

5 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0028

0x1b6862…e19c

4 touches
1 conflict

0xba5743c7…21bf

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

6 conflicts on slot 0x348fda08cf…fc7e96

← previous block·next block →recent activity