← previous blocknext block →recent activity

Analyzing

Block #75,478,945

35 transactions · 25 stateful · 2026-05-18 21:27:57 UTC

Parallelism

63/100

Blocked

72%

Avg conflicts / tx

1.94

Longest chain

13 deep

Execution timeline

did this block parallelize well?

view

block #75,478,945  ·  35 txs across 13 waves  ·  depth 13
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

wave w12

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

0x538c01a3…9a76

0xd32edf…ff58

13 touches
21 conflicts

0x17606ba6…1b6e

0x754704…b603

12 touches
15 conflicts

0x00000000…0004

0x9b60e5…f8ac

10 touches
10 conflicts

0x751db0c0…4f57

0xd18b7e…414b

10 touches
10 conflicts

0xe75ce681…ba5f

0x188d58…ea8e

10 touches
10 conflicts

0xe75ce681…ba61

0x188d58…ea8e

10 touches
10 conflicts

0x51ca3051…0972

0x3bd359…433a

10 touches
10 conflicts

0x00000000…0000

0x614b85…a284

10 touches
10 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 0x538c01a39b…459a76

← previous block·next block →recent activity