← previous blocknext block →recent activity

Analyzing

Block #75,505,949

29 transactions · 19 stateful · 2026-05-19 00:33:17 UTC

Parallelism

62/100

Blocked

58%

Avg conflicts / tx

1.93

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #75,505,949  ·  29 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

0xb1c3152e…2530

0xd32edf…ff58

21 touches
55 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x32b392d9…7f69

0x188d58…ea8e

2 touches
0 conflicts

0x32b392d9…7f6a

0x188d58…ea8e

2 touches
0 conflicts

0xb0a603a9…b124

0x188d58…ea8e

2 touches
0 conflicts

0xb0a603a9…b125

0x188d58…ea8e

2 touches
0 conflicts

0x00000000…0012

0x1b6862…e19c

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

55 conflicts on slot 0xb1c3152ea4…ea2530

← previous block·next block →recent activity