← previous blocknext block →recent activity

Analyzing

Block #75,196,969

17 transactions · 11 stateful · 2026-05-17 14:03:08 UTC

Parallelism

82/100

Blocked

36%

Avg conflicts / tx

0.29

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #75,196,969  ·  17 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x1ce7f59c…b0a4

0xd32edf…ff58

5 touches
3 conflicts

0x4aa4f53b…899f

0x188d58…ea8e

4 touches
1 conflict

0x5860c4f3…0c39

0x3bd359…433a

4 touches
1 conflict

0x4aa4f53b…89a0

0x188d58…ea8e

4 touches
1 conflict

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0x12309510…0ac2

0x000000…012a

4 touches
1 conflict

0x00000000…0002

0xbab229…9388

4 touches
1 conflict

0x00000000…0003

0xbab229…9388

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

3 conflicts on slot 0x1ce7f59c56…d7b0a4

← previous block·next block →recent activity