← previous blocknext block →recent activity

Analyzing

Block #75,479,184

54 transactions · 31 stateful · 2026-05-18 21:29:39 UTC

Parallelism

85/100

Blocked

55%

Avg conflicts / tx

1.07

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #75,479,184  ·  54 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0xe377d6cd…b010

0xd32edf…ff58

13 touches
21 conflicts

0x17606ba6…1b6e

0x754704…b603

12 touches
15 conflicts

0x846f2172…fd54

0x0555e3…2b9c

10 touches
10 conflicts

0x00000000…0004

0x9b60e5…f8ac

8 touches
6 conflicts

0x00000000…0002

0x9b60e5…f8ac

8 touches
6 conflicts

0x00000000…0000

0x9b60e5…f8ac

8 touches
6 conflicts

0x0dbf9688…c6cf

0xd18b7e…414b

8 touches
6 conflicts

0x5dfa485c…cf52

0x754704…b603

8 touches
6 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

21 conflicts on slot 0xe377d6cd28…87b010

← previous block·next block →recent activity