← previous blocknext block →recent activity

Analyzing

Block #75,470,049

24 transactions · 20 stateful · 2026-05-18 20:28:43 UTC

Parallelism

75/100

Blocked

60%

Avg conflicts / tx

1.04

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #75,470,049  ·  24 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

0xded5ec0c…f0fc

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0018

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0028

0x1b6862…e19c

8 touches
6 conflicts

0x8a35acfb…d1a7

0x8d66a4…3095

8 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0xba5743c7…21bf

0x1b6862…e19c

8 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

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: 0x34b6552d…112a6f

6 conflicts on slot 0xded5ec0c97…40f0fc

← previous block·next block →recent activity