← previous blocknext block →recent activity

Analyzing

Block #75,478,693

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

Parallelism

69/100

Blocked

61%

Avg conflicts / tx

1.8

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #75,478,693  ·  35 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0xe52f4789…3d9d

0xd32edf…ff58

21 touches
55 conflicts

0x17606ba6…1b6e

0x754704…b603

8 touches
6 conflicts

0x846f2172…fd54

0x0555e3…2b9c

6 touches
3 conflicts

0x01e7b865…6e6f

0x188d58…ea8e

4 touches
1 conflict

0x46cb45de…a566

0x188d58…ea8e

4 touches
1 conflict

0x46cb45de…a567

0x188d58…ea8e

4 touches
1 conflict

0x66de0ce3…337a

0x188d58…ea8e

4 touches
1 conflict

0x66de0ce3…337b

0x188d58…ea8e

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

55 conflicts on slot 0xe52f4789d3…b13d9d

← previous block·next block →recent activity