← previous blocknext block →recent activity

Analyzing

Block #75,479,189

40 transactions · 22 stateful · 2026-05-18 21:29:41 UTC

Parallelism

85/100

Blocked

45%

Avg conflicts / tx

0.63

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #75,479,189  ·  40 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

0x37a8b8aa…ed08

0xd32edf…ff58

11 touches
15 conflicts

0x00000000…0000

0x9b60e5…f8ac

6 touches
3 conflicts

0xee0a9ebb…c425

0x0555e3…2b9c

6 touches
3 conflicts

0x00000000…0004

0x9b60e5…f8ac

6 touches
3 conflicts

0x17606ba6…1b6e

0x754704…b603

6 touches
3 conflicts

0x5dfa485c…cf52

0x754704…b603

6 touches
3 conflicts

0x37d49489…9309

0x34b655…2a6f

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

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

15 conflicts on slot 0x37a8b8aa22…71ed08

← previous block·next block →recent activity