← previous blocknext block →recent activity

Analyzing

Block #75,140,454

11 transactions · 8 stateful · 2026-05-17 07:45:39 UTC

Parallelism

82/100

Blocked

13%

Avg conflicts / tx

0.18

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #75,140,454  ·  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

0xef17b8cd…9511

0x34b655…2a6f

4 touches
1 conflict

0xf06c2cf5…61bd

0x34b655…2a6f

4 touches
1 conflict

0x3e49348b…9445

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x5adfabe3…e783

0x065c9d…c394

2 touches
0 conflicts

0x5d4771af…99c5

0x065c9d…c394

2 touches
0 conflicts

0x87d7c0b8…7364

0x065c9d…c394

2 touches
0 conflicts

0x948235ef…f525

0x065c9d…c394

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: 0x34b6552d…112a6f

1 conflict on slot 0xef17b8cd5c…709511

← previous block·next block →recent activity