← previous blocknext block →recent activity

Analyzing

Block #75,677,339

14 transactions · 11 stateful · 2026-05-19 19:40:20 UTC

Parallelism

79/100

Blocked

18%

Avg conflicts / tx

0.29

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #75,677,339  ·  14 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

0x5f77d607…2c84

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xfd2e5b6c…72f2

0x065c9d…c394

4 touches
1 conflict

0x2f88a23f…9dc5

0x2a68ba…90c5

4 touches
1 conflict

0x99a21305…dffc

0x2a68ba…90c5

4 touches
1 conflict

0x6f4168b3…cbf5

0x065c9d…c394

4 touches
1 conflict

0x892daf6e…48d8

0x065c9d…c394

4 touches
1 conflict

0x6c956b24…4aae

0x065c9d…c394

3 touches
1 conflict

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

3 conflicts on slot 0x5f77d60791…b12c84

← previous block·next block →recent activity