← previous blocknext block →recent activity

Analyzing

Block #75,087,914

6 transactions · 5 stateful · 2026-05-17 01:55:11 UTC

Parallelism

67/100

Blocked

20%

Avg conflicts / tx

0.17

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #75,087,914  ·  6 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

0x77ad85bf…a1e9

0x065c9d…c394

4 touches
1 conflict

0xb8710eba…489c

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x140ddcdd…6c5d

0x065c9d…c394

2 touches
0 conflicts

0x1aff7968…db30

0x065c9d…c394

2 touches
0 conflicts

0x348fda08…7e96

0x065c9d…c394

2 touches
0 conflicts

0x71fad1d6…9f31

0x065c9d…c394

2 touches
0 conflicts

0xf06bc9b9…d2ef

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

1 conflict on slot 0x77ad85bfef…2ea1e9

← previous block·next block →recent activity