← previous blocknext block →recent activity

Analyzing

Block #75,552,029

35 transactions · 21 stateful · 2026-05-19 05:43:32 UTC

Parallelism

69/100

Blocked

67%

Avg conflicts / tx

1.74

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #75,552,029  ·  35 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0xec016360…6bd3

0xd32edf…ff58

21 touches
55 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x443a3e47…f4a4

0x065c9d…c394

6 touches
3 conflicts

0x2f88a23f…9dc5

0x2a68ba…90c5

6 touches
3 conflicts

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0x00000000…0019

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0029

0x1b6862…e19c

4 touches
1 conflict

0x6aa624fd…a84c

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

55 conflicts on slot 0xec016360dd…276bd3

← previous block·next block →recent activity