← previous blocknext block →recent activity

Analyzing

Block #75,103,198

9 transactions · 8 stateful · 2026-05-17 03:37:03 UTC

Parallelism

67/100

Blocked

38%

Avg conflicts / tx

0.44

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #75,103,198  ·  9 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

0x33018431…8f5f

0x188d58…ea8e

6 touches
3 conflicts

0x33018431…8f5c

0x188d58…ea8e

6 touches
3 conflicts

0x3b99eb5d…2c0a

0x188d58…ea8e

6 touches
3 conflicts

0x12309510…0ac2

0x000000…012a

6 touches
3 conflicts

0x17606ba6…1b6e

0x754704…b603

6 touches
3 conflicts

0x3b99eb5d…2c09

0x188d58…ea8e

6 touches
3 conflicts

0xb0f4dbcb…926a

0x754704…b603

4 touches
1 conflict

0xe069120c…952c

0x000000…012a

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: 0x188d586d…f9ea8e

3 conflicts on slot 0x330184318b…418f5f

← previous block·next block →recent activity