← previous blocknext block →recent activity

Analyzing

Block #75,104,052

15 transactions · 14 stateful · 2026-05-17 03:42:45 UTC

Parallelism

80/100

Blocked

14%

Avg conflicts / tx

0.2

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #75,104,052  ·  15 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…8f5c

0x188d58…ea8e

6 touches
3 conflicts

0x17606ba6…1b6e

0x754704…b603

6 touches
3 conflicts

0x12309510…0ac2

0x000000…012a

6 touches
3 conflicts

0x33018431…8f5d

0x188d58…ea8e

4 touches
1 conflict

0x3b99eb5d…2c0a

0x188d58…ea8e

4 touches
1 conflict

0x3b99eb5d…2c09

0x188d58…ea8e

4 touches
1 conflict

0x33018431…8f5f

0x188d58…ea8e

4 touches
1 conflict

0xcd621226…2df8

0x368ee5…7ca4

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

3 conflicts on slot 0x330184318b…418f5c

← previous block·next block →recent activity