← previous blocknext block →recent activity

Analyzing

Block #75,079,061

13 transactions · 12 stateful · 2026-05-17 00:55:56 UTC

Parallelism

85/100

Blocked

17%

Avg conflicts / tx

0.23

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #75,079,061  ·  13 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0x01e7b865…6e6d

0x188d58…ea8e

4 touches
1 conflict

0x01e7b865…6e6e

0x188d58…ea8e

4 touches
1 conflict

0x348fda08…7e96

0x065c9d…c394

4 touches
1 conflict

0xa66b9f82…2ea7

0xd32edf…ff58

3 touches
1 conflict

0x01e7b865…6e70

0x188d58…ea8e

2 touches
0 conflicts

0x10af039b…4bb5

0x188d58…ea8e

2 touches
0 conflicts

0x10af039b…4bb6

0x188d58…ea8e

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: 0x754704bc…afb603

1 conflict on slot 0x17606ba612…ea1b6e

← previous block·next block →recent activity