← previous blocknext block →recent activity

Analyzing

Block #75,097,729

11 transactions · 9 stateful · 2026-05-17 03:00:34 UTC

Parallelism

82/100

Blocked

22%

Avg conflicts / tx

0.18

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #75,097,729  ·  11 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

0xbfe3d887…654f

0x065c9d…c394

4 touches
1 conflict

0xe2184ec5…93e5

0x065c9d…c394

4 touches
1 conflict

0xbaabd65a…066e

0x065c9d…c394

3 touches
1 conflict

0xb49b4421…4613

0x065c9d…c394

3 touches
1 conflict

0x5d82c9b5…004c

0x3bd359…433a

2 touches
0 conflicts

0x00000000…0004

0x5afd3e…7620

2 touches
0 conflicts

0xc4669269…29f1

0x5afd3e…7620

2 touches
0 conflicts

0xd26c99ca…59ff

0x5afd3e…7620

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: 0x065c9d28…a9c394

1 conflict on slot 0xbfe3d88769…29654f

← previous block·next block →recent activity