← previous blocknext block →recent activity

Analyzing

Block #75,478,229

39 transactions · 25 stateful · 2026-05-18 21:23:07 UTC

Parallelism

62/100

Blocked

80%

Avg conflicts / tx

3.13

Longest chain

15 deep

Execution timeline

did this block parallelize well?

view

block #75,478,229  ·  39 txs across 15 waves  ·  depth 15
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

wave w13

wave w14

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

0x74255f64…e270

0xd32edf…ff58

29 touches
105 conflicts

0xe75ce681…ba61

0x188d58…ea8e

10 touches
10 conflicts

0x0dbf9688…c6cf

0xd18b7e…414b

10 touches
10 conflicts

0xe75ce681…ba5f

0x188d58…ea8e

10 touches
10 conflicts

0x17606ba6…1b6e

0x754704…b603

8 touches
6 conflicts

0x846f2172…fd54

0x0555e3…2b9c

8 touches
6 conflicts

0x00000000…0003

0xd2634e…53b1

6 touches
3 conflicts

0x00000000…0002

0xd2634e…53b1

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

105 conflicts on slot 0x74255f644f…5be270

← previous block·next block →recent activity