← previous blocknext block →recent activity

Analyzing

Block #75,479,296

35 transactions · 21 stateful · 2026-05-18 21:30:26 UTC

Parallelism

74/100

Blocked

57%

Avg conflicts / tx

1.17

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #75,479,296  ·  35 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0xf1bd2969…0ea7

0xd32edf…ff58

17 touches
36 conflicts

0x46cb45de…a568

0x188d58…ea8e

4 touches
1 conflict

0xee0a9ebb…c425

0x0555e3…2b9c

4 touches
1 conflict

0x443a3e47…f4a4

0x065c9d…c394

4 touches
1 conflict

0x46cb45de…a566

0x188d58…ea8e

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0x5dfa485c…cf52

0x754704…b603

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

36 conflicts on slot 0xf1bd29696c…270ea7

← previous block·next block →recent activity